Troutman Pepper Locke, LLP
bd_b936c7af67804f65 · schema v1 · pii pii-v2
Full breach record for Troutman Pepper Locke, 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
2nd time we attacked them in a year (first time through physical intrusion), will continue our attacks...
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Aug 18, 2026
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 (3) · sorted by filing gap
- Vermont State AGbd_0131eb833ce226052026-10-28 · +71dCandidate
- California State AGbd_b0f1346e298396892026-10-28 · +71dVerified
- Texas State AGbd_6da373774778c9762026-10-30 · +73dVerified
Filing propagation · 3 filings · 3 states
View merged incident ↗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