Tom Lange Company, Inc.
bd_ebdafd68f6e6cb25 · schema v1 · pii pii-v1
Full breach record for Tom Lange Company, Inc. →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Blackbyte 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 4, 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
- Indiana State AGbd_060ffcd89da31e8c2022-03-03 · +150dVerified by operator
- Massachusetts State AGbd_481e063e9ea9b6822022-03-03 · +150dVerified by operator
- New Hampshire State AGbd_15615410edae8b0b2022-03-07 · +154dVerified by operator
Filing propagation · 4 filings · 3 states
View merged incident ↗Pattern: first filing Oct 4, last Mar 7 (NH) — a 154-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.
blackbyte
According to ransomware.live, Ransomware. Uses dropper written in JavaScript to deploy a .NET payload.