PRENTKE ROMICH COMPANY
bd_96781319d3fe8f86 · schema v1 · pii pii-v1
Full breach record for PRENTKE ROMICH COMPANY →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Fog 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
250 GB
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Sep 18, 2024
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 (9) · sorted by filing gap
- HHS OCRbd_3534a44b649488432024-09-25 · +6dVerified
- California State AGbd_848e7cd93d7ca5ec2024-09-25 · +6dVerified
- Washington State AGbd_89db2b0c000a38ce2024-09-25 · +6dVerified
- Indiana State AGbd_05a162b64afeee2c2024-09-12 · +7dVerified
Show 5 more filings ↓Show fewer ↑up to 18d gap
- Montana State AGbd_09af3448d15112fb2024-09-12 · +7dVerified
- Massachusetts State AGbd_317e64acdb906ee12024-09-12 · +7dVerified
- New Hampshire State AGbd_347c6a13e03a974d2024-09-12 · +7dVerified
- Vermont State AGbd_6b1745cca9569fa62024-09-12 · +7dVerified
- Illinois State AGbd_d8ea69e00ed094a62024-09-01 · +18dCandidate
Filing propagation · 9 filings · 9 states
View merged incident ↗Pattern: first filing Sep 1 (IL), last Sep 25 (WA) — a 24-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.
fog
According to ransomware.live, Fog, which uses the .flocked extension for encrypted files, was first observed in May in campaigns by Storm-0844, a threat actor known for distributing Akira. By June, Storm-0844 was deploying Fog more than Akira.