THE JOHNS HOPKINS UNIVERSITY
bd_5c01ed35dab04431 · 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 - Johns Hopkins University
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jul 10, 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_8ddec3a29b43d16a2023-07-21 · +10dVerified by operator
- Washington State AGbd_8a0c7a805f112ccb2023-07-25 · +14dVerified
- California State AGbd_aaab7b2385df4fc12023-07-25 · +14dVerified by operator
- Vermont State AGbd_6e8361a25d3114312023-06-23 · +18dVerified by operator
Filing propagation · 4 filings · 4 states
View merged incident ↗Pattern: first filing Jun 23 (VT), last Jul 25 (CA) — a 32-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.