Richmond Public Schools was listed on 10 November 2026 by the interlock ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). interlock listed 13 organizations that month and 151 in total.
- Listed 8 days ago.
- 906 organizations were listed by all groups in November 2026, see the month.
- 36 in Education that month.
- 392 in US that month.
Updated 2026-11-14 16:01 UTC. Data: public leak-site listings. How we work.
Richmond Public Schools
Threat Group Post & Evidence
- Listed by
- Interlock 151 listings in total
The listing states no data size and no ransom demand.
No capture of the original post
We only show a screenshot when we captured the group's own page ourselves. For this listing we have not, so none is shown.
The group's leak-site address is on paid plans
Free accounts see who listed this organization, when, and what the post claims. The address of the group's own page is shown to license-key holders. If you have a key, see what a license key adds.
What the group says it holds
Taken from the group's own post. Ransomware Tracker by ExposureDrift has not seen the data and cannot confirm any of this.
Richmond Public Schools (RPS) is a public school district in Virginia's capital city. The district has an enrollment of 22,000 to 24,000 students and includes 25 elementary schools, 7 middle schools, 5 comprehensive high schools, and 3 specialized schools. Due to a lax approach to security and an unwillingness to negotiate, we are releasing their confidential data, including disciplinary records, medical records, speech therapy and mental health records, special needs education records, and personally identifiable information (names, birth dates, addresses, Social Security numbers, etc.). This breach violates the Federal Education Rights and Privacy Act (FERPA), Virginia privacy laws, and HIPAA, undermines the public trust, and exposes RPS to reputational damage and lawsuits from students, parents, and staff.
Kinds of data mentioned
-
Medical or patient records
“…Federal Education Rights and Privacy Act (FERPA), Virginia privacy laws, and HIPAA, undermines the public trust, and exposes RPS to reputational damage and lawsuits from students,…”
-
Customer or client data
“…public trust, and exposes RPS to reputational damage and lawsuits from students, parents, and staff.”
-
Employee and HR records
“…exposes RPS to reputational damage and lawsuits from students, parents, and staff.”
What to do about this listing
Choose who you are. Each step shows why it appears and, where we have one, its source. General guidance, not legal or incident-response advice.
If you work with Richmond Public Schools (customer, supplier or partner)
Within 3 days
- Do not open the group's page or download the data Do not visit the leak site or download files from a listing. Holding stolen data can be unlawful, and the files can carry malware. Wait for the company's own notice. Why: A safety rule for any leak listing.
- Ask Richmond Public Schools directly Write to your contact and ask whether your data, or your access to their systems, is in scope, and ask for a written statement. Your contract or data-protection law may oblige them to tell you if your data is affected: check the notification clause. Why: A listing is only the group's claim; the company is the one who can confirm what was taken.
- Review what Richmond Public Schools can reach of yours List the accounts, API keys, VPN or SSO connections and shared mailboxes this company has with you. Rotate the keys you gave them and remove access they do not need. Why: Access a supplier holds is how a listing about them can become a problem for you.
- Expect convincing phishing Messages that quote real orders, invoices or names are more likely after a leak. Tell finance and the help desk to treat any request from, or about, this company with extra care. Why: The post names: customer or client data, employee and hr records.
- If you share health data with them You may be the data controller, with notification duties of your own. Ask counsel which health-privacy rules apply to you. Why: The post names medical or health data.
Within 30 days
- Keep watching Richmond Public Schools A supplier's listing can change after the first sighting: the group can add data, change the status or publish. Add the company to your supplier list to be told, and check your own domain too. Why: A listing is a moving claim, not a single event. Add to your supplier list Check your own domain
If you are Richmond Public Schools
First 24 hours
- Reset credentials and sessions Force password, API-key and session-token resets for the accounts the post suggests were exposed, enforce phishing-resistant MFA, and revoke OAuth/SSO grants issued before the listing date. Why: The post names: customer or client data.
Within 3 days
- Handle health-data exposure Work out which patient or health records are in scope, apply the health-privacy notification rules that cover them, and prepare patient communications. Why: The post names: medical or patient records.
- Support affected individuals Identify the employees or customers whose identity data may be in scope and offer identity-protection or credit monitoring; brief the help desk on likely phishing. Why: The post names: employee and hr records.
- Check regulatory and stakeholder notification duties United States: state breach-notification laws apply; listed companies may also have SEC Form 8-K Item 1.05 duties for material incidents, and HIPAA applies to health data. Health data adds sector rules. This is general guidance, not legal advice: confirm current rules with counsel. Why: Listing country: United States.
Within 30 days
- Check shared suppliers and software List the suppliers and software you share with other Education organizations and ask them whether they were affected. Why: interlock listed 8 other Education organization(s) in the last 90 days.
General readiness for any ransomware claim (not about this listing)
- Offline, immutable backups and a restore drill Keep backups outside domain-admin reach and practise a restore; a leak does not remove the risk of re-encryption. Why: General practice for any ransomware claim; not specific to this listing.
- Look for mass file access and unusual outbound transfers Review EDR, proxy and identity logs for bulk reads, archive creation and large uploads to file-sharing services. Why: General practice for any ransomware claim; not specific to this listing.
- Phishing-resistant MFA on remote access Enforce MFA on VPN, SSO and admin panels, and retire password-only or SMS-based remote access. Why: General practice for any ransomware claim; not specific to this listing.
Listing details
Listing severity score (heuristic)
69/100 • ELEVATEDA heuristic built from sector, group, data volume and claim details. It is not evidence that a breach occurred or a measure of harm.
External Attack Surface Profile
ASM IntelligenceRun a free passive scan on your own domain to see what an attacker can see from the outside.