Drivestream Inc.
bd_c000a3f70e33a86e · schema v1 · pii pii-v1
Full breach record for Drivestream Inc. →2 incidents on fileThreat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Akira on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
Post text · scraped from the leak site
Drivestream is a management and IT consulting firm specializing i n migrating the enterprise business processes of large and medium sized businesses to the Cloud. We are ready to upload more than 80 GB of private corporate docum ents including: SSNs, family contacts, contact numbers and e-mail addresses of employees and customers, driver licenses, passports etc.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Dec 9, 2024
Claim posted
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Ransomware claims (1)
- Leak Siteakirabd_36b780c5589de4872025-01-07 · +30dVerified by operator
Regulatory filings (9) · sorted by filing gap
- Massachusetts State AGbd_3dfb99c21c1359da2025-11-17 · +343dVerified by operator
- New Hampshire State AGbd_71871211473c181b2025-11-17 · +343dVerified
- Indiana State AGbd_bed2751c7893e79e2025-11-17 · +343dVerified
- Maine State AGbd_ed6a450222836a2e2025-11-17 · +343dVerified
Show 5 more filings ↓Show fewer ↑up to 378d gap
- Nebraska State AGbd_067e8f2ff9d426892025-11-24 · +350dVerified by operator
- Vermont State AGbd_5944246f16139f482025-11-24 · +350dVerified
- Illinois State AGbd_77f23ae34a1f44552025-12-01 · +357dVerified
- California State AGbd_b629ac5a91ff51932025-12-19 · +375dVerified
- Texas State AGbd_69e2d186b91755092025-12-22 · +378dVerified
Filing propagation · 10 filings · 9 states
View merged incident ↗Pattern: first filing Dec 9, last Dec 22 (TX) — a 378-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.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.
akira
According to ransomware.live, The Akira ransomware group is said to have emerged in March 2023, and there's much speculation about its ties to the former CONTI ransomware group. It's worth noting that with the end of CONTI's operation, several affiliates migrated to independent campaigns such as Royal, BlackBasta, and others. According to some reports, Akira affiliates also work with other ransomware operations, such as Snatch and BlackByte, as an open directory of tools used by an Akira operator was identified, which also had connections to the Snatch ransomware. The first version of the Akira ransomware was written in C++ and appended files with the '.akira' extension, creating a ransom note named 'akira_readme.txt,' partially based on the Conti V2 source code. However, on June 29, 2023, a decryptor for this version was reportedly released by Avast. Subsequently, a version was released that fixed the decryption flaw on July 2, 2023. Since then, the new version is said to be written in Rust, this time called 'megazord.exe,' and it changes the extension to '.powerranges' for encrypted files. Most of Akira's initial access vectors use brute-force attempts on Cisco VPN devices (which use single-factor authentication only). Additionally, exploitation of CVEs: CVE-2019-6693 and CVE-2022-40684 for initial access has been identified. Source: https://github.com/crocodyli/ThreatActors-TTPs