ComNet Communications
bd_16f70eb811588143 · schema v1 · pii pii-v1
Full breach record for ComNet Communications →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 : yes
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jul 15, 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 (2) · sorted by filing gap
- Indiana State AGbd_bedfc6bc17574e912024-08-23 · +38dCandidate
- Massachusetts State AGbd_f5f9307a579da4da2024-08-26 · +41dVerified
Filing propagation · 3 filings · 2 states
View merged incident ↗Pattern: first filing Jul 15, last Aug 26 (MA) — a 41-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.