SAINT XAVIER UNIVERSITY
bd_1cc1cbb51e78bb88 · schema v1 · pii pii-v1
Full breach record for SAINT XAVIER UNIVERSITY →Press / market disclosure — not a breach-notification filing
A media or market posting that confirms an incident but carries no breach-notification fields, so compliance clocks aren't assessable. The summary below is extracted from the coverage — verify against the source.
210,000 Impacted by Saint Xavier University Data Breach - SecurityWeek. Saint Xavier University: Saint Xavier University was the victim of a cyberattack that exposed the data of 210,000 individuals. The incident resulted in a leak of confidential data, but details regarding the nature of this information and the attack methods used are not yet available. The university has taken measures to contain the breach and notify affected parties. Linked ransomware group: alphv.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jul 21, 2023
Press report
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Attack → press
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Ransomware claims (1)
- Leak Sitealphvbd_8ccf5c8f1e8552cd2023-08-14 · +24dVerified
Regulatory filings (5) · sorted by filing gap
- Illinois State AGbd_688e3c00de9130292024-10-01 · +438dCandidate
- Vermont State AGbd_08673f526f077e6d2024-10-23 · +460dVerified
- Indiana State AGbd_84d412a28e7d5f4d2024-10-30 · +467dVerified
- Maine State AGbd_e2be20372c5a352e2024-10-30 · +467dVerified
Show 1 more filing ↓Show fewer ↑up to 468d gap
- Massachusetts State AGbd_e4a17068e5d629912024-10-31 · +468dVerified
Filing propagation · 6 filings · 5 states
View merged incident ↗Pattern: first filing Jul 21, last Oct 31 (MA) — a 468-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
- incident type + narrative only (may be machine-translated)
- discovery date
- materiality
- affected count
- data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.
alphv
According to ransomware.live, The operators of the ALPHV/BlackCat ransomware began their activity in December 2021, making posts on Dark Web forums to promote their affiliate program, offering other actors the opportunity to engage in a 'new type of ransomware family' developed from scratch using the Rust programming language. Some clear evidence indicates that the actors behind this new ransomware are not new to cybercrime, and there were links to other affiliate programs such as DarkSide, BlackMatter, and REvil. (After several attacks against large companies, these groups faced pressure and arrests, necessitating the termination of their operations). As a security measure, the operators of ALPHV implemented the requirement for the execution of the ransomware payload by providing an 'access token,' which is supplied by the owners of the Ransomware-as-a-Service to the affiliate. This token is added to the victim's ransom note so that they can contact the threat actor responsible for encrypting the data. ALPHV affiliates employ double and triple extortion techniques, meaning the publication of the company's name on leak sites, threats of data leakage, and lastly, threats of DDoS attacks against the organization. Source: https://github.com/crocodyli/ThreatActors-TTPs