SINCLAIR BROADCAST GROUP, INC.
bd_ea6951a13a3d2bba · schema v1 · pii pii-v1
Full breach record for SINCLAIR BROADCAST GROUP, INC. →2 incidents on fileThreat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Macaw 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
Oct 16, 2021
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 (4) · sorted by filing gap
- Massachusetts State AGbd_b8352dccaf15ea962021-12-16 · +61dVerified by operator
- Indiana State AGbd_c68968727458ced52022-03-24 · +159dVerified by operator
- New Hampshire State AGbd_c59dd08e53a7306d2022-03-31 · +166dVerified by operator
- Illinois State AGbd_3e7ebe34761e492a2021-01-01 · +288dVerified by operator
Filing propagation · 5 filings · 4 states
View merged incident ↗Pattern: first filing Jan 1 (IL), last Mar 31 (NH) — a 454-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.