ATSG, Inc
bd_8a1c957e302701ab · schema v1 · pii pii-v1
Full breach record for ATSG, Inc →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group BianLian 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
ATSG, Inc. was founded in 1994 as an IT solution provider with an initial focus in the enterprise networking arena.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Sep 6, 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 Sitebianlianbd_100fd113149f5bff2024-11-09 · +65dVerified by operator
Regulatory filings (7) · sorted by filing gap
- Pressbianlianbd_c09996ad6c9c2a8e2024-09-06Candidate
- HHS OCRbd_eb6e86fd349f9e632024-10-04 · +28dCandidate
- Massachusetts State AGbd_0e8ceda8da1c00912024-10-05 · +29dVerified by operator
- Indiana State AGbd_5b9b58c33c22b70c2025-02-21 · +168dVerified by operator
Show 3 more filings ↓Show fewer ↑up to 172d gap
- Massachusetts State AGbd_af9e80106bed91992025-02-22 · +169dVerified by operator
- New Hampshire State AGbd_1bf34451981ec1942025-02-25 · +172dVerified by operator
- Maryland State AGbd_b257a36e6d1771342025-02-25 · +172dVerified by operator
Filing propagation · 8 filings · 5 states
View merged incident ↗Pattern: first filing Sep 6, last Feb 25 (MD) — a 172-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.
bianlian
According to ransomware.live, BianLian ransomware operations began in late 2021. The group practices multi-pronged extortion, demanding payment for a decryptor, as well as the non-release of stolen data. The ransomware group hosts a public, TOR-based, blog to post victim identities and stolen data. Somewhat unique to BianLian at the time of their launch was their inclusion of an I2P mirror for their blog.