Social EngineeringEducationEducationPhishingStolen CredentialsMulti-Stage ChainData ExfiltratedCustomer Data InvolvedPIIIdentity (basic)AuthenticationLowContained

Simmons University

bd_c4eddb1389b4b7ff · schema v1 · pii pii-v1

Severity

Low

Discovered

Mar 10, 2025

Filed

Mar 14, 2025

To disclose

4 days

Affected

1state residents only

Linked

3 filings

Confidence

65%

Full breach record for Simmons University →5 incidents on file

Simmons University reported a phishing incident on March 14, 2025, affecting one New Hampshire resident. The breach occurred on March 9, 2025, when an employee clicked a malicious link and provided credentials, allowing unauthorized access to WorkDay. PII was exfiltrated. The incident was contained on March 10. Remediation included account lockdown, forensic investigation, and credit monitoring for the victim.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 1 days

discovery → filing · 4 days

Mar 9, 2025

Begins

Mar 10, 2025

Discovered

Mar 14, 2025

Filed

vs. sector median

6 wks faster

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

Linked disclosures

Why this link?

Regulatory filings (2) · sorted by filing gap

Massachusetts State AGbd_fa04e59dc287a07b2025-03-12 · +2dCandidate
Massachusetts State AGbd_43d1cd65ffbdb7712025-02-21 · +21dCandidate

Name: Simmons University
norm: simmons university
Domain: simmons.edu

Name: Simmons University
norm: simmons university
Domain: simmons.edu
Industry: Educationllm

Discovered: Mar 10, 2025
Breach occurred: Mar 9, 2025 – Mar 9, 2025
Undetected for: 1 dayoccurrence → discovery
Materiality determined: —
Notification sent: Mar 11, 2025
Affected individuals: 1state-resident count only
Data types: PIIIdentity (basic)Authentication
Attack vector: Phishing
MITRE ATT&CK: T1566.002 Spearphishing LinkT1078 Valid Accounts
Threat actor: ExternalFinancial
Initial access: phishing_link

During the incident: Identified and locked compromised accounts to prevent further unauthorized access
Alerted affected employees and initiated account recovery procedures
Investigated potential data access and unauthorized transactions
Engaged with Google and external security partners to take down the phishing site
Issued a security advisory to the Simmons community about the ongoing threat
Enhanced monitoring of university systems for further suspicious activity
Provided free credit monitoring to the affected employees
Changes made: Continue to train people monthly on how to protect themselves against cyber-attacks such as phishing, malware, and social engineering
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 4 days(4 days from discovery to filing)
Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 3 filings · 2 states

View merged incident ↗

Massachusetts State AGFeb 21 · first

Massachusetts State AG+19d

New Hampshire State AG+21d · this page

Pattern: first filing Feb 21 (MA), last Mar 14 (NH) — a 21-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://mm.nh.gov/files/uploads/doj/remote-docs/simmons-university-20250314.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Mar 14, 2025
Raw hash: fd3e8c410e6ab30afed31c618e071c63a4719e120c4da7c0173508d87bf2771b

Linked disclosures

Regulatory filings (2) · sorted by filing gap

Reporting entitySimmons University

Victim entitySimmons University

Incidentdiscovered Mar 10, 2025

Stated responseIdentified and locked compromised accounts to prevent further unauthorized access

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancemm.nh.gov