hccs.edu was listed on 15 June 2026 by the shinyhunters ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). shinyhunters listed 19 organizations that month and 162 in total.
- Listed 156 days ago.
- 708 organizations were listed by all groups in June 2026, see the month.
- 29 in Education that month.
- 199 in US that month.
Updated 2026-11-19 05:42 UTC. Data: public leak-site listings. How we work.
Threat Group Post & Evidence
- Listed by
- Shinyhunters 162 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.
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.
Hundreds of thousands of student records containing full name, home address, phone, email, date of birth, gender, ethnicity, enrollment status, GPA, major, and student ID across all campuses. Daily and full student roster exports library credentials, PINs, and @student[.hccs[.edu accounts. Over 12,000 financial aid and bursar reports including FAFSA/ISIR suspense data with names, birthdates, emails, phones, and home addresses. Class rosters with birthdates, grades, academic programs, and contact information for tens of thousands of enrolled students per term. Over 344,000 international student documents including SEVIS I-20 forms, visa applications, passports, bank statements, tax returns, immigration affidavits, and acceptance letters. Over 14,000 student immunization and vaccination records including meningitis compliance documentation. Over 15,000 additional health and immunization do…
Show the full post (1214 characters)
Hundreds of thousands of student records containing full name, home address, phone, email, date of birth, gender, ethnicity, enrollment status, GPA, major, and student ID across all campuses. Daily and full student roster exports library credentials, PINs, and @student[.hccs[.edu accounts. Over 12,000 financial aid and bursar reports including FAFSA/ISIR suspense data with names, birthdates, emails, phones, and home addresses. Class rosters with birthdates, grades, academic programs, and contact information for tens of thousands of enrolled students per term. Over 344,000 international student documents including SEVIS I-20 forms, visa applications, passports, bank statements, tax returns, immigration affidavits, and acceptance letters. Over 14,000 student immunization and vaccination records including meningitis compliance documentation. Over 15,000 additional health and immunization documents across report archives and A LOT more was compromised. This is a final warning to reach out by 18 June 2026 before we leak along with several annoying (digital) problems that'll come your way. Make the right decision, don't be the next headline. | Updated: 16 June 2026 | Warning: FINAL WARNING PAY OR LEAK
Kinds of data mentioned
-
Tax records
“…including SEVIS I-20 forms, visa applications, passports, bank statements, tax returns, immigration affidavits, and acceptance letters. Over 14,000 student immunization…”
-
Identity documents
“…Over 344,000 international student documents including SEVIS I-20 forms, visa applications, passports, bank statements, tax returns, immigration affidavits, and acceptance…”
-
Passwords and credentials
“…ID across all campuses. Daily and full student roster exports library credentials, PINs, and @student[.hccs[.edu accounts. Over 12,000 financial aid and bursar reports including…”
-
Email and communications
“…thousands of student records containing full name, home address, phone, email, date of birth, gender, ethnicity, enrollment status, GPA, major, and student ID across all…”
-
Customer or client data
“Hundreds of thousands of student records containing full name, home address, phone, email, date of birth, gender, ethnicity,…”
Plain-English summary AI-written
The group says it holds student records, student roster exports, financial aid and bursar reports, class rosters, and international student documents, including personal, academic, financial, and immigration information.
Written by an AI model (openai/gpt-6-luna) from the post above. It can contain mistakes: rely on the quote, not the summary.
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 hccs.edu (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 hccs.edu 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 hccs.edu 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, email and communications, passwords and credentials, identity documents.
- Verify payment-detail changes by phone Confirm any change to bank details or any urgent invoice with a number you already hold, not one in the message. Why: The post names: tax records.
Within 30 days
- Keep watching hccs.edu 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 hccs.edu
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: passwords and credentials, identity documents, email and communications, customer or client data.
Within 3 days
- 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: identity documents.
- Check for mailbox compromise Audit mailbox rules, forwarding and delegated access, rotate mail-admin credentials and move DMARC to p=reject to limit follow-on phishing. Why: The post names: email and communications.
- Lock down exposed admin, VPN and SSO panels Restrict by IP allow-list or a zero-trust proxy and require MFA. Why: A passive scan found 3 critical panel(s) reachable from the internet.
- 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. This is general guidance, not legal advice: confirm current rules with counsel. Why: Listing country: United States.
Within 30 days
- Watch for tax-filing fraud Tell your tax advisers and, where available, tax authorities so fraudulent filings made with exposed identifiers can be caught early. Why: The post names: tax records.
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.