St. Lucie County Tax Collector's Office
bd_4e5ff0a8dbf9c19a · schema v1 · pii pii-v1
Full breach record for St. Lucie County Tax Collector's Office →3 incidents on fileThreat-actor claim — not a regulatory filing
This row is a claim by the ransomware group ALPHV / BlackCat 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
Proof of Leakage First part listing Full data dump soon... - more personal data with SSN, address, DOB, DL, W4, W9, CC
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Nov 13, 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?Regulatory filings (9) · sorted by filing gap
- Montana State AGbd_3287d0543d75ae4d2023-12-28 · +45dVerified by operator
- Massachusetts State AGbd_4b9a5dc6bbd1b5e02023-12-28 · +45dVerified by operator
- Indiana State AGbd_696eeff6d4ebe4be2023-12-28 · +45dVerified by operator
- Vermont State AGbd_b07011eb179ec5c32023-12-28 · +45dVerified
Show 5 more filings ↓Show fewer ↑up to 149d gap
- New Hampshire State AGbd_b9f4ab32f0094c952023-12-28 · +45dVerified by operator
- Maine State AGbd_c255febf4c5222bc2023-12-28 · +45dVerified by operator
- Maine State AGbd_1adb356afa9d45202024-04-10 · +149dVerified by operator
- New Hampshire State AGbd_70eeb649da68ed312024-04-10 · +149dVerified by operator
- Vermont State AGbd_eac607cf8f8cbff12024-04-10 · +149dVerified by operator
Filing propagation · 10 filings · 6 states
View merged incident ↗Pattern: first filing Nov 13, last Apr 10 (VT) — a 149-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.
alphv
According to ransomware.live, The operators of the ALPHV/BlackCat ransomware began their activity in December 2021, making posts on Dark Web forums to promote their affiliate program, offering other actors the opportunity to engage in a 'new type of ransomware family' developed from scratch using the Rust programming language. Some clear evidence indicates that the actors behind this new ransomware are not new to cybercrime, and there were links to other affiliate programs such as DarkSide, BlackMatter, and REvil. (After several attacks against large companies, these groups faced pressure and arrests, necessitating the termination of their operations). As a security measure, the operators of ALPHV implemented the requirement for the execution of the ransomware payload by providing an 'access token,' which is supplied by the owners of the Ransomware-as-a-Service to the affiliate. This token is added to the victim's ransom note so that they can contact the threat actor responsible for encrypting the data. ALPHV affiliates employ double and triple extortion techniques, meaning the publication of the company's name on leak sites, threats of data leakage, and lastly, threats of DDoS attacks against the organization. Source: https://github.com/crocodyli/ThreatActors-TTPs