J.McLaughlin
bd_baf77f75aa322c90 · schema v1 · pii pii-v1
Full breach record for J.McLaughlin →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Blackmatter 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
Sep 20, 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 (3) · sorted by filing gap
- New Hampshire State AGbd_62592626346b65992022-01-11 · +113dVerified
- Maine State AGbd_929a3a530c51c9662022-01-11 · +113dCandidate
- Massachusetts State AGbd_dd602d57530174b82022-01-11 · +113dVerified by operator
Filing propagation · 4 filings · 3 states
View merged incident ↗Pattern: first filing Sep 20, last Jan 11 (MA) — a 113-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.
blackmatter
According to ransomware.live, Ransomware-as-a-Service