Texas Wesleyan University
bd_e514341c78236cc6 · schema v1 · pii pii-v1
Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Cl0p 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
Post text · scraped from the leak site
Home - Texas Wesleyan University
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Nov 25, 2023
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 (4) · sorted by filing gap
- Montana State AGbd_0e17c2357de3c9972023-11-20 · +6dVerified by operator
- Massachusetts State AGbd_d12ddf10fe3107b82024-01-30 · +65dVerified by operator
- New Hampshire State AGbd_74a5812548adb5ed2024-02-12 · +78dCandidate
- Maine State AGbd_0f5d664addff81e32024-07-29 · +246dVerified
Filing propagation · 4 filings · 4 states
View merged incident ↗Pattern: first filing Nov 20 (MT), last Jul 29 (ME) — a 252-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.