Newegg
ent_4eaea9855b443fa2a5d59844
Disclosures
5
State AG · 5 jurisdictions
Incidents
1
filings grouped by incident
Max affected reported
20,231
as filed · State AG OR
Leak-site claims
0
none in sample
Identity resolution
- Canonical name
- Newegg
- Normalized
- newegg— dedupe via name-norm; Microsoft / MSFT collapse to one row
- GLEIF LEI
- No match
- SEC EDGAR CIK
- None — not an SEC registrant
- Domain
- newegg.com
Disclosure history (5)newest first
- 🌴South Carolina State AGas victim2018-11-19
Newegg, Inc. submitted a breach notification to the South Carolina Office of the Attorney General on December 19, 2018. The provided source document is a PDF placeholder with no extracted text content, preventing extraction of incident specifics, affected counts, or data types.
- 🌲Washington State AGas victim2018-11-15
Newegg Inc., a business sector entity reported a malware incident to the Washington Attorney General. The organization became aware of the incident on 2018-09-18 and filed notice on 2018-11-15. 5,931 Washington residents were affected. 58 days elapsed between awareness and notification. 36 days to identify the breach. 1 days to contain the breach.
- 🦬Montana State AGas victim2018-11-15
Newegg reported a data breach to the Montana Attorney General. The breach was reported on 2018-11-15. The breach occurred from 8/13/2018 to 9/19/2018. 651 Montana residents were affected.
- 🐻California State AGas victim2018-11-15
Newegg Inc. notified California regulators of a data breach affecting customers who placed orders between August 13, 2018, and September 19, 2018. Unauthorized access to checkout servers resulted in the collection of customer names, addresses, and payment card details (including CVV2). Newegg engaged a security firm, removed malicious code, secured servers, and reported the incident to law enforcement and payment networks.
- 🦫Oregon State AGas victim2018-11-15
Newegg Inc. reported a data breach to the Oregon Attorney General. The breach was reported on 2018-11-15. The breach occurred during 8/13/2018 - 8/13/2018. The breach was discovered on 10/23/2018. 20,231 individuals were affected. Notice was sent on 9/19/201811/15/2018.