Black, Bashor & Porsch, LLP
bd_aff43ae730429091 · schema v1 · pii pii-v1
Full breach record for Black, Bashor & Porsch, LLP →2 incidents on fileThreat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Silentransomgroup 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
Accounting Services
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jan 14, 2025
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 (2) · sorted by filing gap
- New Hampshire State AGbd_119632f74de1c6b52025-01-24 · +9dVerified
- Indiana State AGbd_e2cde23331696fd82025-01-24 · +9dCandidate
Filing propagation · 3 filings · 2 states
View merged incident ↗Pattern: first filing Jan 14, last Jan 24 (IN) — a 9-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.
silentransomgroup
According to ransomware.live, a former Conti team