The City of Cocoa
bd_fd2e128aa9b3f361 · schema v1 · pii pii-v1
Full breach record for The City of Cocoa →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group INC Ransom 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
The City of Cocoa offers diverse public services aimed at enhancing the quality of life for its community. Their services include water management, economic development programs, and various community engagement initiatives. Intended clients encompass local residents, businesses, and visitors who seek information and support from city departments. The city is also focused on maintaining public safety, health, and environmental stewardship.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Feb 16, 2026
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 Siteinc_ransombd_a8dc5eead01258242026-02-23 · +7dCandidate
Regulatory filings (1) · sorted by filing gap
- Maine State AGbd_5cd78ce5db30aa152026-06-04 · +108dVerified by operator
Filing propagation · 2 filings
View merged incident ↗Pattern: first filing Feb 16, last Jun 4 (ME) — a 108-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.