Enterprise Bank and Trust Company
bd_ca4f3a81100467bc · 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
Post text · scraped from the leak site
Enterprise Bank
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jul 26, 2023
Claim posted
—
Corroborated · see linked filings
This record's own dates cannot anchor compliance clocks; see the linked filings.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (4) · sorted by filing gap
- Vermont State AGbd_a5756f65ca3456db2023-08-07 · +12dVerified by operator
- Massachusetts State AGbd_3567d4db5edda8732023-09-07 · +43dVerified by operator
- New Hampshire State AGbd_4920e1793ad684922023-09-07 · +43dVerified by operator
- Maine State AGbd_b19276c8873bf3ea2023-09-07 · +43dVerified by operator
Filing propagation · 4 filings · 4 states
View merged incident ↗Pattern: first filing Aug 7 (VT), last Sep 7 (ME) — a 31-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.