Drivestream Inc.
bd_ed6a450222836a2e · schema v1 · pii pii-v1
Full breach record for Drivestream Inc. →2 incidents on fileDrivestream Inc. reported an external system breach (hacking) occurring between Dec 4-9, 2024. An unauthorized actor accessed systems and potentially exfiltrated data including names, SSNs, and financial account info. One Maine resident was affected. Notification was sent Nov 17, 2025. Law enforcement was notified, and credit monitoring was offered.
J jump to incidentP pin to compareR raw source
Incident timeline
Dec 4, 2024
Begins
Dec 9, 2024
Discovered
Nov 17, 2025
Filed
vs. sector median
+30 wks slower
Linked disclosures
Why this link?Ransomware claims (2)
- Leak Siteakirabd_36b780c5589de4872025-01-07 · +313dVerified by operator
- Leak Siteakirabd_c000a3f70e33a86e2024-12-09 · +343dVerified by operator
Regulatory filings (8) · sorted by filing gap
- Massachusetts State AGbd_3dfb99c21c1359da2025-11-17Verified by operator
- New Hampshire State AGbd_71871211473c181b2025-11-17Verified
- Indiana State AGbd_bed2751c7893e79e2025-11-17Verified
- Nebraska State AGbd_067e8f2ff9d426892025-11-24 · +7dVerified by operator
Show 4 more filings ↓Show fewer ↑up to 35d gap
- Vermont State AGbd_5944246f16139f482025-11-24 · +7dVerified
- Illinois State AGbd_77f23ae34a1f44552025-12-01 · +14dVerified
- California State AGbd_b629ac5a91ff51932025-12-19 · +32dVerified
- Texas State AGbd_69e2d186b91755092025-12-22 · +35dVerified
Filing propagation · 9 filings · 9 states
View merged incident ↗Pattern: first filing Nov 17 (MA), last Dec 22 (TX) — 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.