Chicago History Museum was listed on 08 September 2026 by the incransom ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). incransom listed 29 organizations that month and 1044 in total.
- Listed 72 days ago.
- 874 organizations were listed by all groups in September 2026, see the month.
- 42 in Education that month.
- 272 in US that month.
Updated 2026-11-19 05:29 UTC. Data: public leak-site listings. How we work.
Chicago History Museum
Threat Group Post & Evidence
- Listed by
- INC Ransom 1,044 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.
# CHICAGO HISTORY MUSEUM — DATA BREACH  **Organization:** Chicago History Museum (formerly Chicago Historical Society) **Location:** 1601 N Clark Street, Chicago, IL 60614 **Website:** chicagohistory.org **CEO:** Michael J. Anderson, President & CEO **Industry:** Non-profit / Cultural Institution **Breach Date:** September 2026 **Data Volume:** 4 departments + AWS cloud infrastructure, 15+ years of records **Individuals Affected:** 20,000+ --- ## WHAT HAPPENED Chicago History Museum's internal file server **and** AWS cloud infrastructure have been fully compromised. Sensitive data from four departments and the production cloud environment has been exfiltrated: **From Internal File Server:** - **IT Credentials** — AWS root keys, server passwords, BitLocker encryption keys, 20+ vendor portal logins in plaintext - **Accounting & Finance** — 15 years of ADP payroll…
Show the full post (8949 characters)
# CHICAGO HISTORY MUSEUM — DATA BREACH  **Organization:** Chicago History Museum (formerly Chicago Historical Society) **Location:** 1601 N Clark Street, Chicago, IL 60614 **Website:** chicagohistory.org **CEO:** Michael J. Anderson, President & CEO **Industry:** Non-profit / Cultural Institution **Breach Date:** September 2026 **Data Volume:** 4 departments + AWS cloud infrastructure, 15+ years of records **Individuals Affected:** 20,000+ --- ## WHAT HAPPENED Chicago History Museum's internal file server **and** AWS cloud infrastructure have been fully compromised. Sensitive data from four departments and the production cloud environment has been exfiltrated: **From Internal File Server:** - **IT Credentials** — AWS root keys, server passwords, BitLocker encryption keys, 20+ vendor portal logins in plaintext - **Accounting & Finance** — 15 years of ADP payroll records (2006–2021), bank reconciliations, audit workpapers, ACH authorization documents - **Human Resources** — Employee background checks containing Social Security Numbers, I-9 immigration documents, personal identity verification forms - **Development / Institutional Advancement** — Board of Trustees home addresses, major donor pledge records ($4.4M+ in named donations), corporate funder relationships, donor CRM exports **From AWS Cloud (Account 187824323586):** - **Production Database** — Full access to Aurora MySQL containing the museum's website, 27,422 form submissions with visitor personal data - **14 EC2 Servers** — Complete control of production, staging, and scaling infrastructure - **S3 Backups** — 20 GB of website backups (146,000 files) — the only cloud backup - **27,422 Public Records** — Names, emails, phone numbers, and personal details of museum visitors, event clients, school field trip contacts, donor applicants, interns, and volunteers collected over 7 years --- ## DATA SAMPLES ### 🔑 IT Credentials Exposed in Plaintext AWS root account access keys, BitLocker disk encryption recovery key, and passwords for Adobe, Microsoft, Blackbaud (donor payment platform), Symantec, and 20+ grant portals including Boeing, ComEd, Exelon, MacArthur Foundation, SAM.gov, and City of Chicago. *See: Screenshots 01–05* ### 👥 Board of Trustees — Home Addresses Full names, home addresses, ZIP codes, and spouse names for 40+ members of the Board of Trustees, including prominent Chicago families residing in Lake Shore Drive, Winnetka, Lake Forest, Hinsdale, and Gold Coast neighborhoods. *See: Screenshot 06* ### 💰 Donor Pledge Records — Named Amounts Capital Campaign Endowment pledge details totaling $4,460,684 from Board of Trustees members, including individual named amounts ranging from $2,000 to $700,650. Corporate donors include Molex Inc., First Chicago NBD, LaSalle National Bank, Crate & Barrel, and Commonwealth Edison. Notable: Donald Rumsfeld — $50,000 pledge documented. *See: Screenshot 07* ### 📊 15 Years of Payroll Data ADP payroll general ledger reports from 2006 through 2021 containing employee compensation details, benefit allocations, and salary breakdowns for all museum staff. *See: Screenshot 08* ### 🔒 Employee SSN & Background Checks Background check documents for 20+ employees including SSA-89 Social Security verification forms, I-9 immigration employment authorization documents, and personal identification records. Under the Illinois Personal Information Protection Act (PIPA), this constitutes a reportable data breach requiring notification to the Illinois Attorney General and all affected individuals within 45 days. *See: Screenshot 09* ### 🏗️ Complete IT Infrastructure Server inventory (20 servers, VMware ESXi environment), full Cisco network topology (5 switches, 450+ patch panel mappings), VLAN architecture, external IP ranges, and firewall configuration. Multiple Windows Server 2003 systems still operational. *See: Screenshots 10–11* ### 🏦 Banking Records & Prior Fraud 14 years of bank reconciliation files (BMO Harris, Northern Trust), ACH authorization lists, W-9 tax forms, and documentation of a prior ACH fraud incident in April 2015. *See: Screenshot 12* --- ### ☁️ AWS Cloud — Full Infrastructure Control Using the AWS root access keys found on the file server, we accessed the museum's entire cloud environment: - **AWS Account 187824323586** — root-level access, no MFA - **Aurora MySQL Production Database** — full DBA privileges with GRANT OPTION. Dumped 127 tables from the production site database and 119 tables from the staging database - **27,422 contact form submissions** from 2016–2023 — names, emails, phone numbers, home addresses, and messages from visitors, wedding/corporate event clients, school field trip coordinators, collection donors, internship applicants, and volunteers - **14 EC2 instances** (13 currently running) — Master Server, Scaler, Staging, Elastic Beanstalk environments - **6 S3 buckets** — 20 GB of website backups, CDN content, and encyclopedia resources - **2 CloudFront distributions** — content delivery infrastructure - **30 WordPress admin accounts** with password hashes extracted - **MySQL port 3306 publicly accessible** with no IP restrictions — a textbook security failure **This means we have the ability to shut down the museum's website, delete all cloud backups, and wipe the production database at any time. The museum's RDS instance has zero snapshots — deletion is permanent.** *See: Screenshots 16–17* ### 👨👩👧👦 Public & Visitor Data — 20,000+ Individuals The production database contained form submissions from 54 different contact forms spanning 7 years: | Form | Records | Data Collected | |------|---------|---------------| | Contact Us | 11,779 | Name, email, message | | Event Inquiries (weddings, corporate) | 4,848 | Name, phone, email, company, event details | | School Field Trip Reservations | 3,887 | School name, teacher name, phone, email, student count | | Collection Donations | 2,263 | Donor name, contact info, item descriptions | | Internship Applications | 458 | Personal details of applicants | | Volunteer Applications | 138 | Personal details | | COVID-19 Submissions | 420 | Personal health-related data | | Other forms | 3,629 | Various PII | | **TOTAL** | **27,422** | | This is not just an employee data breach. **Over 20,000 members of the public** — including parents of schoolchildren, wedding couples, corporate event planners, donors, and job applicants — will need to be notified under Illinois law. *See: Screenshot 18* --- ## WHAT WE WANT **We have contacted Chicago History Museum management directly.** They have been given a deadline to respond and begin negotiations. **If no response is received by the deadline, the full dataset will be published on this page**, including: - All credentials and access keys (unredacted) - Complete Board of Trustees personal information - All named donor amounts and corporate funder records - Employee SSN and background check documents - Full server/network infrastructure details - Banking records and audit workpapers - **27,422 visitor/public contact records (names, emails, phones)** - **Production database SQL dumps** - **WordPress admin credentials** Additionally, the museum's AWS cloud infrastructure remains under our control. Non-cooperation will result in **permanent destruction of the production website, databases, and all cloud backups.** --- ## COUNTDOWN ⏱️ **Publication deadline: [DATE + 4 DAYS]** The museum's management has been notified. The clock is ticking. --- ## WHY THIS MATTERS Chicago History Museum is a **501(c)(3) non-profit** that relies on public trust, donor confidence, and government grant funding. A public data leak of this scale would: 1. **Trigger mandatory breach notification for 20,000+ individuals** — under Illinois PIPA, every employee whose SSN was exposed AND every member of the public whose personal data was in the contact forms must be notified, along with the Illinois Attorney General 2. **Destroy donor trust** — named donation amounts are considered strictly confidential in the non-profit sector 3. **Endanger Board members** — home addresses of 40+ prominent Chicago families published online 4. **Jeopardize grant funding** — Boeing, MacArthur, ComEd, Exelon, Abbott, and other institutional funders have strict data security requirements 5. **Expose the organization to class-action litigation** from 20,000+ affected individuals — employees, visitors, donors, schools, and Board members 6. **Generate massive media coverage** — Chicago Tribune, Sun-Times, Block Club Chicago, and national arts media. The story writes itself: "Museum that preserves history can't protect its own data" 7. **Destroy the website and all digital operations** — we retain the ability to permanently take down chicagohistory.org and all cloud infrastructure Management has a simple choice: respond now, or deal with all of the above.
Amounts as written
- 20 GB
- 146,000 files
- 20+ employees
Kinds of data mentioned
-
Tax records
“…reconciliation files (BMO Harris, Northern Trust), ACH authorization lists, W-9 tax forms, and documentation of a prior ACH fraud incident in April 2015. *See: Screenshot…”
-
Accounting and ledgers
“…passwords, BitLocker encryption keys, 20+ vendor portal logins in plaintext - **Accounting & Finance** — 15 years of ADP payroll records (2006–2021), bank reconciliations, audit workpapers,…”
-
Payroll and salaries
“…portal logins in plaintext - **Accounting & Finance** — 15 years of ADP payroll records (2006–2021), bank reconciliations, audit workpapers, ACH authorization documents -…”
-
Identity documents
“…documents - **Human Resources** — Employee background checks containing Social Security Numbers, I-9 immigration documents, personal identity verification forms - **Development /…”
-
Passwords and credentials
“…environment has been exfiltrated: **From Internal File Server:** - **IT Credentials** — AWS root keys, server passwords, BitLocker encryption keys, 20+ vendor portal logins in…”
-
Email and communications
“…(146,000 files) — the only cloud backup - **27,422 Public Records** — Names, emails, phone numbers, and personal details of museum visitors, event clients, school field trip…”
-
Customer or client data
“…emails, phone numbers, and personal details of museum visitors, event clients, school field trip contacts, donor applicants, interns, and volunteers collected over 7 years…”
-
Employee and HR records
“…audit workpapers, ACH authorization documents - **Human Resources** — Employee background checks containing Social Security Numbers, I-9 immigration documents, personal…”
-
Contracts and legal files
“…data security requirements 5. **Expose the organization to class-action litigation** from 20,000+ affected individuals — employees, visitors, donors, schools, and Board members…”
-
Databases and backups
“…CRM exports **From AWS Cloud (Account 187824323586):** - **Production Database** — Full access to Aurora MySQL containing the museum's website, 27,422 form submissions with…”
Plain-English summary AI-written
The group says it holds sensitive data from four museum departments and its production cloud environment, spanning more than 15 years of records.
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 Chicago History Museum (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 Chicago History Museum 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 Chicago History Museum 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, 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: payroll and salaries, accounting and ledgers, tax records.
- Check software and integrations you take from them If you run their software or call their API, check that updates come through the usual channel and rotate the keys and tokens you hold for it. Why: The post names: databases and backups.
Within 30 days
- Keep watching Chicago History Museum 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 Chicago History Museum
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, 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: payroll and salaries, accounting and ledgers.
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.
- Rotate database and cloud access Rotate database and cloud-storage keys, review public bucket and snapshot sharing, turn on object-level audit logging and keep backup encryption keys separate. Why: The post names: databases and backups.
- 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.
- 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: 20 GB, 146,000 files, 20+ employees. Treat group figures as unverified.
- 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
- Review privileged and contract material Ask counsel which contracts and privileged files are named, and whether client or partner confidentiality terms oblige you to tell them. Why: The post names: contracts and legal files.
- 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.
- Check shared suppliers and software List the suppliers and software you share with other Education organizations and ask them whether they were affected. Why: incransom 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)
88/100 • CRITICALA 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 IntelligenceNo scan has been run for this domain yet, so there are no figures to show. Running one is passive: it reads public DNS and certificate records only.
Open the full attack surface scan →Run a free passive scan on your own domain to see what an attacker can see from the outside.