HackingEducationEducationStolen CredentialsData ExfiltratedTargetedPIIIdentity (basic)LowContained

Asbury Theological Seminary

bd_c23b589b8418a769 · schema v1 · pii pii-v1

Severity

Low

Discovered

Jun 6, 2024

Filed

Mar 10, 2025

To disclose

40 weeks

Affected

Not disclosed

Linked

9 filings

Confidence

64%

Full breach record for Asbury Theological Seminary →

Asbury Theological Seminary notified affected individuals of a data security incident detected on June 6, 2024. Unauthorized access occurred between June 1-6, 2024. Personal information was potentially accessed. The Seminary engaged external cybersecurity professionals and forensic investigators. Affected individuals were offered credit monitoring services and advised on fraud alerts.

J jump to incidentP pin to compareR raw source

Maryland clock✗ MD AG >90d40 weeks discovery → filing

Incident timeline

undetected · 5 days

discovery → filing · 40 weeks / 277 days

Jun 1, 2024

Begins

Jun 6, 2024

Discovered

Mar 10, 2025

Filed

vs. sector median

+29 wks slower

This filing is one of 9 about the same incident.View merged incident

A leak claim by fog about this victim predates this filing by 259 days.View originating leak claim

Linked disclosures

Why this link?

Ransomware claims (1)

Leak Sitefogbd_501367b8b3dd67a12024-06-24 · +259dVerified by operator

Regulatory filings (7) · sorted by filing gap

Indiana State AGbd_24f57d2c0053855f2025-03-10Verified
Montana State AGbd_657ecb51549b10982025-03-10Candidate
Maine State AGbd_a993b38d52acc7762025-03-10Verified
Nebraska State AGbd_d0638871479380a72025-03-10Verified

Show 3 more filings ↓up to 365d gap

Massachusetts State AGbd_7b45acd9970e486f2025-03-11 · +1dVerified by operator
New Hampshire State AGbd_9a35a11c50a1633e2025-03-14 · +4dVerified
Vermont State AGbd_b468f324db2dfd8a2024-03-10 · +365dVerified by operator

Name: Asbury Theological Seminary
norm: asbury theological seminary

Name: Asbury Theological Seminary
norm: asbury theological seminary
Industry: Educationllm

Discovered: Jun 6, 2024
Breach occurred: Jun 1, 2024 – Jun 6, 2024
Undetected for: 5 daysoccurrence → discovery
Materiality determined: —
Notification sent: Mar 9, 2025
Affected individuals: Not disclosed
Data types: PIIIdentity (basic)
Attack vector: Unauthorized Access
MITRE ATT&CK: T1078 Valid Accounts
Threat actor: External
Regulator citations: Notified Maryland Attorney General Consumer Protection Division
Initial access: valid_credentials

During the incident: Secured the environment
Commenced a prompt and thorough investigation
Worked very closely with external cybersecurity professionals
Conducted an extensive forensic investigation
Conducted a manual document review
Offering a complimentary membership of Experian IdentityWorksSM Credit 3B
Advising the affected residents about the process for placing a fraud alert and/or security freeze on their credit files
Providing the contact information for the consumer reporting agencies, the Federal Trade Commission and the Maryland Attorney General Consumer Protection Division
Set up a dedicated and confidential toll-free response line
Changes made: Continually evaluates and modifies its practices and internal controls to enhance the security and privacy of personal information
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 40 weeks(277 days from discovery to filing)
Compliance flags: MD AG >90dLeak >180d
Discovery-date grounding: letter-groundedThe discovery date is the detection date narrated in the notification letter — the defensible tier.

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 8 filings · 8 states

View merged incident ↗

Vermont State AGMar 10 · first

Indiana State AG+365d

Montana State AG+365d

Maine State AG+365d

Nebraska State AG+365d

Maryland State AG+365d · this page

Massachusetts State AG+366d

New Hampshire State AG+369d

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

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://oag.maryland.gov/resources-info/SBN%20Documents/2025/ITU-376521.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Mar 10, 2025
Raw hash: 3deb0910b7fb67604e4a1ed8845b28d473b9abd537931451e2796c32f5b41108

Linked disclosures

Ransomware claims (1)

Regulatory filings (7) · sorted by filing gap

Reporting entityAsbury Theological Seminary

Victim entityAsbury Theological Seminary

Incidentdiscovered Jun 6, 2024

Stated responseSecured the environment

ComplianceMD AG >90d

Extraction provenanceno artifact recorded

Source provenanceoag.maryland.gov