CRB GROUP, INC.
bd_e71f054d4e07a83e · schema v1 · pii pii-v1
Full breach record for CRB GROUP, INC. →2 incidents on fileThreat-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
A revolutionary integrated project delivery method that leverages the combined expertise and technical excellence of ONE project team to deliver your facility in a safe, lean and collaborative way. Engineering Architecture Construction Consulting The...
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Dec 24, 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 (5) · sorted by filing gap
- Montana State AGbd_1b0368e8efedb4bb2024-08-21 · +241dCandidate
- New Hampshire State AGbd_49ff40255db6cfb52024-08-21 · +241dVerified
- Maine State AGbd_5e29086617cf07f22024-08-21 · +241dVerified by operator
- Indiana State AGbd_d7da9110f4502c632024-08-21 · +241dVerified
Show 1 more filing ↓Show fewer ↑up to 241d gap
- Massachusetts State AGbd_f6db377cc4e5b1212024-08-21 · +241dVerified
Filing propagation · 6 filings · 5 states
View merged incident ↗Pattern: first filing Dec 24, last Aug 21 (MA) — a 241-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.