Collabera
bd_83c901139b1156f8 · schema v1 · pii pii-v1
Full breach record for Collabera →Collabera, Inc. reported a ransomware incident to New Hampshire. Unauthorized access began May 24, 2020, and was detected June 8, 2020. The incident likely impacted 129 NH employees' PII, including SSNs and DOB. Collabera restored data from backups, engaged forensic experts, and offered 2 years of credit monitoring.
J jump to incidentP pin to compareR raw source
Incident timeline
May 24, 2020
Begins
Jun 8, 2020
Discovered
Jul 17, 2020
Filed
vs. sector median
13 wks faster
Linked disclosures
Why this link?Ransomware claims (1)
- Leak Sitemazebd_5d5bd239a535e0f92020-06-08 · +39dVerified by operator
Regulatory filings (7) · sorted by filing gap
- Oregon State AGbd_534cb167d91a2bab2020-07-21 · +4dVerified
- Massachusetts State AGbd_a1782f53e1d2060f2020-07-21 · +4dVerified
- California State AGbd_b7536fb665576b4c2020-07-21 · +4dVerified
- Indiana State AGbd_041bbb0ab945452d2020-07-10 · +7dVerified by operator
Show 3 more filings ↓Show fewer ↑up to 8d gap
- Delaware State AGbd_8d1bb831591496b22020-07-10 · +7dVerified by operator
- Washington State AGbd_889cc32e696bff5c2020-07-09 · +8dVerified
- Montana State AGbd_e6483d8e749b4d982020-07-09 · +8dVerified
Filing propagation · 8 filings · 8 states
View merged incident ↗Pattern: first filing Jul 9 (WA), last Jul 21 (CA) — a 12-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.