Prince George's County Public Schools
bd_d6c0f52f7e7c7bba · schema v1 · pii pii-v1
Full breach record for Prince George's County Public Schools →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.
Prince George's County Public Schools impacted by cyberattack. Prince George's County Public Schools: Monday morning, Prince George's County Public Schools were the victim of a cyberattack. According to PGCPS, the attack affected 4,500 user accounts out of 180,000, primarily staff accounts. The main business and student information systems, Oracle and SchoolMAX, do not appear to have been affected. Although many network systems have been restored, all users will need to reset their passwords on August 15. PGCPS will contact affected users in the coming days with more information regarding their accounts, pending further review by a team of cyber experts. Linked ransomware group: rhysida.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Aug 14, 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 (2)
- Leak Siterhysidabd_a20f01bece62e63c2023-08-25 · +11dVerified by operator
- Leak Siterhysidabd_8ae5e09ce762a9922023-08-14Verified by operator
Regulatory filings (5) · sorted by filing gap
- Indiana State AGbd_08eab472eefc37222024-02-14 · +184dVerified by operator
- Vermont State AGbd_aad486a5dc9671092024-02-16 · +186dVerified by operator
- Maine State AGbd_b45517379abebaaa2024-02-16 · +186dVerified by operator
- Massachusetts State AGbd_e096a863b1d43bee2024-02-16 · +186dVerified by operator
Show 1 more filing ↓Show fewer ↑up to 196d gap
- New Hampshire State AGbd_e614eab3878f05a22024-02-26 · +196dVerified by operator
Filing propagation · 6 filings · 5 states
View merged incident ↗Pattern: first filing Aug 14, last Feb 26 (NH) — a 196-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.
rhysida
According to ransomware.live, Rhysida is a ransomware-as-a-service (RAAS) group that emerged in May 2023. The group utilizes a namesake ransomware through phishing attacks and Cobalt Strike to breach the targets' networks and deploy their payloads. The group threatens to publicly distribute exfiltrated data if the ransom is not paid, and it's worth mentioning that Rhysida is still in the early stages of development. The ransomware leaves PDF notes in the affected folders, instructing victims to contact the group through its portal, and payment is made via Bitcoin. After encryption, the ransomware appends the extension '.ryshida' to encrypted files. Source: https://github.com/crocodyli/ThreatActors-TTPs