BACKROADS
bd_94c7105fbcd61d63 · schema v1 · pii pii-v1
Full breach record for BACKROADS →Backroads experienced a ransomware incident where files were encrypted and data was exfiltrated prior to encryption. The company became aware of suspicious activity on October 2, 2020. The breach affected 16 New Hampshire residents, exposing names, dates of birth, SSNs, government IDs, financial account info, and health insurance info. Backroads engaged forensic specialists, secured the network, and is rebuilding it. Credit monitoring is being offered.
J jump to incidentP pin to compareR raw source
Incident timeline
Oct 2, 2020
Discovered
Nov 24, 2020
Filed
vs. sector median
10 wks faster
Linked disclosures
Why this link?Regulatory filings (6) · sorted by filing gap
- Massachusetts State AGbd_6eadb352e50544e02020-11-19 · +5dVerified
- California State AGbd_7381ee0e20a518532020-11-19 · +5dVerified
- Montana State AGbd_8d5027cb14bd22ed2020-11-19 · +5dCandidate
- Maine State AGbd_b3d7644895863e402020-11-19 · +5dVerified
Show 2 more filings ↓Show fewer ↑up to 111d gap
- California State AGbd_e286b5f31a42b0a52021-02-26 · +94dVerified
- New Hampshire State AGbd_ac67e485d6963e4b2021-03-15 · +111dVerified
Filing propagation · 7 filings · 5 states
View merged incident ↗Pattern: first filing Nov 19 (MA), last Mar 15 (NH) — a 116-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.