McKim & Creed, Inc.
bd_cb261d405b1bdf2c · schema v1 · pii pii-v1
Full breach record for McKim & Creed, Inc. →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group LockBit 3.x 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.
Sanctions caution: LockBit 3.x carries US sanctions exposure — OFAC has designated the group or its operators. Public reporting is permitted (informational-materials exemption, 50 U.S.C. § 1702(b)(3)) — but any payment or material support may violate sanctions. Consult counsel before engaging.
Source: Ransomware.live
Post text · scraped from the leak site
Family. And we treat our clients, and each other, like family. Employee-owned engineering and surveying firm with offices in North Carolina, South Carolina, Florida, Georgia, Virginia, Texas, Pennsylvania & Louisiana.You can contact the main syst...
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Mar 14, 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?Ransomware claims (1)
- Leak Siteransomhubbd_387d9fc205ef80ac2024-03-13 · +1dVerified by operator
Regulatory filings (5) · sorted by filing gap
- Indiana State AGbd_f5a31b083e15de5a2024-02-28 · +16dVerified by operator
- Montana State AGbd_2a4b99f921839eb32024-06-06 · +83dVerified by operator
- Maine State AGbd_7e06855add24fd9f2024-06-06 · +83dVerified by operator
- Massachusetts State AGbd_90da3079f7832cf82024-06-06 · +83dVerified by operator
Show 1 more filing ↓Show fewer ↑up to 83d gap
- Vermont State AGbd_faaca113c940adb52024-06-06 · +83dVerified by operator
Filing propagation · 6 filings · 5 states
View merged incident ↗Pattern: first filing Feb 28 (IN), last Jun 6 (VT) — a 99-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.