ExecuPharm Inc.
bd_acab60010fa7e557 · schema v1 · pii pii-v1
Full breach record for ExecuPharm Inc. →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
Mar 13, 2020
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_a8470fac8c8d843f2020-03-16 · +3dVerified
- Massachusetts State AGbd_4ea2294527b6a2902020-04-16 · +34dVerified by operator
- New Hampshire State AGbd_dcfeb26245f9198d2020-04-17 · +35dVerified
- Indiana State AGbd_f96df19d63ead0bd2020-04-17 · +35dVerified by operator
Filing propagation · 5 filings · 4 states
View merged incident ↗Pattern: first filing Mar 13, last Apr 17 (IN) — a 35-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.