Asbury Theological Seminary
bd_501367b8b3dd67a1 · schema v1 · pii pii-v1
Full breach record for Asbury Theological Seminary →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
10 GB
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jun 24, 2024
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 (8) · sorted by filing gap
- Vermont State AGbd_b468f324db2dfd8a2024-03-10 · +106dVerified by operator
- Indiana State AGbd_24f57d2c0053855f2025-03-10 · +259dVerified
- Montana State AGbd_657ecb51549b10982025-03-10 · +259dCandidate
- Maine State AGbd_a993b38d52acc7762025-03-10 · +259dVerified
Show 4 more filings ↓Show fewer ↑up to 263d gap
- Maryland State AGbd_c23b589b8418a7692025-03-10 · +259dVerified by operator
- Nebraska State AGbd_d0638871479380a72025-03-10 · +259dVerified
- Massachusetts State AGbd_7b45acd9970e486f2025-03-11 · +260dVerified by operator
- New Hampshire State AGbd_9a35a11c50a1633e2025-03-14 · +263dVerified
Filing propagation · 9 filings · 8 states
View merged incident ↗Pattern: first filing Mar 10 (VT), last Mar 14 (NH) — a 369-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.