Custom Security Systems
bd_6a1153385676842f · schema v1 · pii pii-v1
Full breach record for Custom Security Systems →Threat-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 : no
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Sep 5, 2024
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 (3) · sorted by filing gap
- Maine State AGbd_49129a40216cceac2025-07-29 · +326dVerified by operator
- Indiana State AGbd_7d54d44885e7739a2025-07-29 · +326dVerified
- Massachusetts State AGbd_abae6e3edaa2b8252025-07-30 · +327dVerified by operator
Filing propagation · 4 filings · 3 states
View merged incident ↗Pattern: first filing Sep 5, last Jul 30 (MA) — a 327-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.