DG3 NORTH AMERICA, INC.
bd_c9f1cd861768c280 · schema v1 · pii pii-v1
Full breach record for DG3 NORTH AMERICA, INC. →3 incidents on fileDG3 North America, Inc. reported a ransomware cyber incident affecting 2,670 Washington residents. Unauthorized access to personal information (names, addresses, dates of birth) occurred between February 5 and March 22, 2024. DG3 discovered the incident on March 19, 2024, engaged forensic specialists, notified law enforcement, and provided 24 months of credit monitoring.
J jump to incidentP pin to compareR raw source
Incident timeline
Feb 5, 2024
Begins
Mar 19, 2024
Discovered
Jul 26, 2024
Filed
vs. sector median
on median
Linked disclosures
Why this link?Regulatory filings (8) · sorted by filing gap
- Vermont State AGbd_27c5b3f7791858d92024-07-03 · +23dVerified
- California State AGbd_7cc0ccf7210e21452024-07-03 · +23dVerified
- Indiana State AGbd_97d8ee49b95cb7a52024-07-03 · +23dVerified
- New Hampshire State AGbd_a80b2d135dc215072024-07-03 · +23dVerified
Show 4 more filings ↓Show fewer ↑up to 56d gap
- Maine State AGbd_fa12d9a2227192932024-07-03 · +23dVerified
- Montana State AGbd_1e3d7f4f2e934bbe2024-05-31 · +56dCandidate
- Maine State AGbd_465aad9ab025282a2024-05-31 · +56dCandidate
- Massachusetts State AGbd_8d48d4c1e95140492024-05-31 · +56dVerified
Filing propagation · 9 filings · 8 states
View merged incident ↗Pattern: first filing May 31 (MT), last Jul 26 (WA) — a 56-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.