KMB Design Group
bd_7ed01aef5132a6ae · schema v1 · pii pii-v1
Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Black Basta 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
KMB is a full service engineering solutions provider licensed in the US and Europe developing comprehensive solutions for our clients.SITE: www.kmbdg.com Address : 1800 State Rte 34 Ste 209 Belmar, NJ, 07719 USAALL DATA SIZE: ~1.5tb 1. Projects (current and old) 2. Accounting 3. Users (employees personal folders and documents) & etc...
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Mar 19, 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 (4) · sorted by filing gap
- Montana State AGbd_0f27edb48e447d962025-01-28 · +315dCandidate
- Indiana State AGbd_5e2942bb3bab66cb2025-01-28 · +315dVerified
- Nebraska State AGbd_8efe069c9be5da2a2025-01-28 · +315dVerified
- Massachusetts State AGbd_62d1868cdc71ca8a2025-01-29 · +316dVerified
Filing propagation · 5 filings · 4 states
View merged incident ↗Pattern: first filing Mar 19, last Jan 29 (MA) — a 316-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.