TWU Local 100
bd_4cde0d138cbb2a22 · schema v1 · pii pii-v1
Full breach record for TWU Local 100 →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Qilin 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
Feb 3, 2026
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 (5) · sorted by filing gap
- Indiana State AGbd_02a456927aea01292026-04-24 · +80dVerified by operator
- Indiana State AGbd_36f2deae02d39a282026-04-24 · +80dVerified
- Vermont State AGbd_972f7a479631d7552026-04-24 · +80dVerified
- Massachusetts State AGbd_b1c4e7ab687bca142026-04-24 · +80dVerified by operator
Show 1 more filing ↓Show fewer ↑up to 80d gap
- New Hampshire State AGbd_c859070a609e7efb2026-04-24 · +80dVerified
Filing propagation · 5 filings · 4 states
View merged incident ↗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.
qilin
According to ransomware.live, Qilin ransomware was first observed in July of 2022. Qilin Ransomware is written in Golang and supports multiple encryption modes; all of which are controlled by the operator. Qilin actors practice double extortion – demanding payment for a decryptor, as well as for the non-release of stolen data.