Kannact
bd_3577dae43c860326 · schema v1 · pii pii-v1
Full breach record for Kannact →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Cl0p 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
Kannact
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Mar 23, 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 (10) · sorted by filing gap
- New Hampshire State AGbd_94cb9ce753b551842023-04-18 · +26dVerified
- HHS OCRbd_7385e75f799452482023-06-20 · +89dVerified by operator
- Indiana State AGbd_1e6199d96e8d96ed2023-08-14 · +144dVerified
- Montana State AGbd_2bbf967b1d0ff94c2023-09-21 · +182dVerified
Show 6 more filings ↓Show fewer ↑up to 201d gap
- Maine State AGbd_07529270f797a54a2023-09-22 · +183dVerified
- Massachusetts State AGbd_80f53accc2f0e5622023-09-22 · +183dVerified
- Oregon State AGbd_c082f97720f3e6962023-09-22 · +183dVerified
- California State AGbd_cd661c6340a504802023-09-22 · +183dVerified
- New Hampshire State AGbd_4b9e8cf6b4ed74b12023-09-29 · +190dVerified
- Montana State AGbd_29de722ce2bf8e1f2023-10-10 · +201dVerified
Showing first 10 of 13 linked disclosures.
Filing propagation · 11 filings · 7 states
View merged incident ↗Pattern: first filing Mar 23, last Oct 10 (MT) — a 201-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Cascade drawn from the first 10 linked disclosures of 13 — the full spread may be wider.
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.