Delphinus Engineering
bd_d980d8c17ac51fca · schema v1 · pii pii-v1
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
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jan 1, 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
- Maine State AGbd_03f9ee8c8af817be2024-04-10 · +99dCandidate
- Indiana State AGbd_7bb74435197eb8fe2024-04-10 · +99dVerified
- New Hampshire State AGCL0Pbd_b3d7b5e65594463c2024-04-10 · +99dVerified
- Massachusetts State AGbd_d0544ae773a49c192024-04-12 · +101dVerified by operator
Filing propagation · 5 filings · 4 states
View merged incident ↗Pattern: first filing Jan 1, last Apr 12 (MA) — a 101-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.