Kotz Sangster Wysocki
bd_e43e9a7b3f37dea6 · schema v1 · pii pii-v1
Full breach record for Kotz Sangster Wysocki →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Silentransomgroup 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
Law Firms & Legal Services
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Dec 13, 2024
Claim posted
—
Corroborated · see linked filings
This record's own dates cannot anchor compliance clocks; see the linked filings.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (3) · sorted by filing gap
- Massachusetts State AGbd_849d4dcf8aab2aca2025-01-03 · +20dVerified
- Indiana State AGbd_e4365d44a6e7db902025-01-03 · +20dCandidate
- Maryland State AGbd_125bd4b4a7d174c32026-05-19 · +522dVerified by operator
Filing propagation · 3 filings · 3 states
View merged incident ↗Pattern: first filing Jan 3 (MA), last May 19 (MD) — a 502-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.
silentransomgroup
According to ransomware.live, a former Conti team