Asbury Automotive Group, Inc.
bd_61315dea1c4d6b6d · schema v1 · pii pii-v1
Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Cactus 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
Download link #1: https://***************.onion/ABG/PROOF
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jan 12, 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?Regulatory filings (6) · sorted by filing gap
- Maine State AGbd_128bda9c925acce52024-04-24 · +102dCandidate
- Montana State AGbd_1f650bcc4c18cb842024-04-24 · +102dVerified
- New Hampshire State AGbd_2f4692a880bce6542024-04-24 · +102dVerified
- Vermont State AGbd_4ddce7a31b86d2c52024-04-24 · +102dVerified
Show 2 more filings ↓Show fewer ↑up to 102d gap
- Indiana State AGbd_92252072357742dd2024-04-24 · +102dVerified
- Massachusetts State AGbd_ea73e323df49c9f52024-04-24 · +102dVerified
Filing propagation · 7 filings · 6 states
View merged incident ↗Pattern: first filing Jan 12, last Apr 24 (MA) — a 102-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.
cactus
According to ransomware.live, The CACTUS ransomware is said to have emerged around March 2023. The group became known for exploiting vulnerabilities to gain initial access and maintain a presence within the organization's infrastructure. There is little known information about the ransomware group, except that it emerged on the mentioned date and, following encryption, a text file named 'cAcTuS.readme.txt' would be created. Additionally, encrypted files were altered to the '.cts1' extension, and data exfiltration and victim extortion were conducted through the use of the service known as Tox. Source: https://github.com/crocodyli/ThreatActors-TTPs