AutoZone, Inc.
bd_8e8b2610b911309a · schema v1 · pii pii-v1
Full breach record for AutoZone, Inc. →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Dispossessor 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
autozone.com
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Apr 19, 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 Sitecl0pbd_194dee6c6b6f32a02023-07-07 · +287dVerified by operator
Regulatory filings (8) · sorted by filing gap
- Washington State AGbd_a895d70c2f1e3c602023-11-22 · +149dVerified
- Vermont State AGbd_2e82b08f0d975f282023-11-21 · +150dVerified
- Massachusetts State AGbd_6ec1d040bec779f62023-11-21 · +150dVerified
- Oregon State AGbd_e2dcaa9f4f49c3c52023-11-21 · +150dVerified
Show 4 more filings ↓Show fewer ↑up to 474d gap
- California State AGbd_0809502990bdba432023-11-20 · +151dVerified
- Montana State AGbd_367ded5d15c02eb12023-11-20 · +151dVerified
- Maine State AGbd_547d20145f6a4aa82023-11-20 · +151dVerified
- Illinois State AGbd_959f6ace42ee32a42023-01-01 · +474dCandidate
Filing propagation · 9 filings · 8 states
View merged incident ↗Pattern: first filing Jan 1 (IL), last Apr 19 — a 474-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.
dispossessor
According to ransomware.live, This is not a ransomware group but a data broker