Veristat Parent, L.P.
bd_6bac5b6661597f3c · schema v1 · pii pii-v1
Full breach record for Veristat Parent, L.P. →Threat-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
Veristat is the science-first full-service drug and biologic CRO and consultancy that integrates strategic planning, regulatory ex pertise, and clinical trial execution to rapidly advance the most complex or novel therapies. We are ready to upload more than 63 GB of essential corporate doc uments such as: HR documents, contact numbers and e-mail addresse s of employees and customers, medicare documents, customer medica l documents, confidential licenses, agreements and contracts, fin ancial data (audits, payment details, reports), etc.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Feb 14, 2025
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_56a0052d3239a5052025-03-11 · +25dVerified by operator
Regulatory filings (4) · sorted by filing gap
- Massachusetts State AGbd_4bf5fb3afb13f6c02025-04-04 · +49dVerified by operator
- Indiana State AGbd_877b9a5ec99e08782025-05-20 · +95dVerified
- New Hampshire State AGbd_98935b939bdac0e12025-05-20 · +95dVerified
- Maine State AGbd_fbb9318b422b65d72025-05-20 · +95dVerified by operator
Filing propagation · 5 filings · 4 states
View merged incident ↗Pattern: first filing Feb 14, last May 20 (ME) — a 95-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