St. Johns River Water Management District
bd_45ae366e4aafcf9d · schema v1 · pii pii-v1
Full breach record for St. Johns River Water Management District →2 incidents on fileThreat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Hunters International 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
Country : United States of America - Exfiltraded data : yes - Encrypted data : yes
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Dec 1, 2023
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?Ransomware claims (1)
- Leak Siteqilinbd_e26e569c7e45fe3e2023-12-01Candidate
Regulatory filings (1) · sorted by filing gap
- Indiana State AGbd_f9b7cf204324d57e2024-02-05 · +65dVerified by operator
Filing propagation · 2 filings
View merged incident ↗Pattern: first filing Dec 1, last Feb 5 (IN) — a 65-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.