EQUIFAX INC.
bd_bf00e329b87159ef · schema v1 · pii pii-v1
Full breach record for EQUIFAX INC. →12 incidents on fileEquifax filed a supplemental notice with the New Hampshire Attorney General on October 12, 2017, updating the scope of the July 2017 breach. The incident, caused by exploitation of a web application vulnerability, impacted approximately 145.5 million U.S. consumers, including 634,614 New Hampshire residents. Data exposed included names, SSNs, DOBs, addresses, and driver's license numbers. Equifax engaged Mandiant for forensics and offered credit monitoring.
J jump to incidentP pin to compareR raw source
Incident timeline
May 15, 2017
Begins
Jul 29, 2017
Discovered
Oct 12, 2017
Filed
vs. sector median
+2 wks slower
Linked disclosures
Why this link?Regulatory filings (6) · sorted by filing gap
- South Carolina State AGbd_20e4e8963ad56aa02017-09-12 · +30dVerified
- California State AGbd_278155640602f8682017-09-07 · +35dVerified
- Washington State AGbd_958fcf9ef068490f2017-09-07 · +35dCandidate
- New Hampshire State AGbd_c7a263041aff38052017-09-07 · +35dCandidate
Show 2 more filings ↓Show fewer ↑up to 35d gap
- Oregon State AGbd_d60b910cf11a2f9c2017-09-07 · +35dVerified
- Massachusetts State AGbd_e7e140ebd326c5762017-09-07 · +35dVerified
Filing propagation · 7 filings · 6 states
View merged incident ↗Pattern: first filing Sep 7 (CA), last Oct 12 (NH) — a 35-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.