Maple Leaf Foods
bd_f57465a68b7d77cb · schema v1 · pii pii-v1
Full breach record for Maple Leaf Foods →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Black Basta 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
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Dec 1, 2022
Claim posted
—
Corroborated · see linked filings
This record's own dates cannot anchor compliance clocks; see the linked filings.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (3) · sorted by filing gap
- Indiana State AGbd_be0d22ca16344e692022-11-22 · +9dVerified by operator
- Massachusetts State AGbd_d224d7b1084da1f62023-01-03 · +33dVerified by operator
- New Hampshire State AGbd_00d6929ecd12c4cc2023-01-30 · +60dVerified by operator
Filing propagation · 3 filings · 3 states
View merged incident ↗Pattern: first filing Nov 22 (IN), last Jan 30 (NH) — a 69-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.