Ransomware Tracker by ExposureDrift
Dashboard / Victims / icc.edu

icc.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.

icc.edu corporate emblem
Listed by shinyhunters Disclosed: 2026-06-15 19:28 UTC

icc.edu

icc.edu Education US

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.

Over 28 gigabytes of Illinois Central College data (122,000+ files) was compromised across PeopleSoft Campus Solutions and Human Resources (ICC, SURS pension reporting, Workday costing, and ICCB curriculum systems), including 9,200+ employee payslip PDFs, 500+ SURS payroll files with Social Security numbers, direct deposit records with bank account and routing numbers, student financial aid and grade roster exports, enrollment CSVs with @icc.edu accounts, and Workday salary allocation data spanning 2021 through June 2026. 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

Amounts as written

  • 28 gigabytes
  • 122,000+ files
  • 9,200+ employee

Kinds of data mentioned

  • Banking and wire details

    “…payroll files with Social Security numbers, direct deposit records with bank account and routing numbers, student financial aid and grade roster exports, enrollment CSVs with…”

  • Payroll and salaries

    “…curriculum systems), including 9,200+ employee payslip PDFs, 500+ SURS payroll files with Social Security numbers, direct deposit records with bank account and routing numbers,…”

  • Identity documents

    “…systems), including 9,200+ employee payslip PDFs, 500+ SURS payroll files with Social Security numbers, direct deposit records with bank account and routing numbers, student financial aid…”

  • Customer or client data

    “…numbers, direct deposit records with bank account and routing numbers, student financial aid and grade roster exports, enrollment CSVs with @icc.edu accounts, and Workday…”

  • Employee and HR records

    “…reporting, Workday costing, and ICCB curriculum systems), including 9,200+ employee payslip PDFs, 500+ SURS payroll files with Social Security numbers, direct deposit records…”

Plain-English summary AI-written

The group says it holds over 28 gigabytes of Illinois Central College data, including employee payroll and banking records, student financial aid and grade information, enrollment records, and salary allocation data.

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 icc.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 icc.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 icc.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, identity documents, employee and hr records.
  • 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: banking and wire details, payroll and salaries.

Within 30 days

  • Keep watching icc.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 icc.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: identity documents, customer or client data, payroll and salaries.
  • Protect payments Tell your bank, verify any change to supplier or payroll bank details by calling a known number, and watch for invoice-fraud emails that use real names and amounts. Why: The post names: banking and wire details, payroll and salaries.

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: employee and hr records, identity documents.
  • Size the exposure against your own systems Inventory which systems hold data of the kind and volume claimed, so notification and legal decisions rest on your records rather than the group's figures. Why: The post claims: 28 gigabytes, 122,000+ files, 9,200+ employee. Treat group figures as unverified.
  • 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 2 critical panel(s) reachable from the internet.
  • Retire staging and dev exposure Take non-production hosts off the internet or behind authentication, and rotate any secrets they held. Why: A passive scan found 1 non-production host(s) that are public.
  • 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.
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

Resolved Domain icc.edu
Industry Vertical Education
Country US
Enrichment Status ENRICHED

Listing severity score (heuristic)

69/100 • ELEVATED

A heuristic built from sector, group, data volume and claim details. It is not evidence that a breach occurred or a measure of harm.

1. Sector Criticality 20/30 pts
Higher education and research
2. Group tier 10/25 pts
Tier 3: all other groups
3. Data Volume & PII Scope 25/25 pts
Largest claim: a terabyte or more, or regulated data named in the post
Formula: sector • group tier • data claimed (scaled to 100) Rule-based score

External Attack Surface Profile

ASM Intelligence
99/100 • CRITICAL
Last Audited: 2026-11-14 16:31 UTC Passive Recon
Total Network Assets 18
7 hosts • 11 unique IPs
0 cloud-hosted • 5 SaaS
Subdomain Assets 7
Critical Panels 2 (VPN/Admin/SSO)
Non-Prod / UAT 1 Staging/Dev
SaaS Ecosystem 5 Cloud Apps
Primary CSP Public Cloud / E
Email Security Grade B (SPF/DMARC)
Open the full attack surface scan →
Is Your Organization Exposed?

Run a free passive scan on your own domain to see what an attacker can see from the outside.

Defense Telemetry

Passive DNS
Mail Gateway Microsoft 365 / Exchange Online
DNS Authority Cloudflare Managed DNS
Edge CDN / Shield Cloudflare CDN / DDoS Shield
SPF Record Configured
DMARC Policy Enforced
Public DNS records only • no port scanning

More Claims by shinyhunters

All →
WARNING
Technology 2026-09-30 00:02 UTC
Final statement re PSA
Technology 2026-09-24 08:44 UTC
Fresenius Medical Care
Healthcare 2026-09-22 22:42 UTC
PSA - READ THIS NOW
Financial Services 2026-09-22 18:51 UTC
Note to Cl0p-_
Unknown 2026-09-20 00:15 UTC
Qi****
Unknown 2026-09-17 01:28 UTC