October's defining breach did not require breaking into a government system. Attackers misused a private Danish company's legitimate access to Denmark's Central Person Register (CPR) and extracted names, addresses and CPR numbers, Denmark's national ID numbers, for about 8.8 million people, Danish authorities announced on October 5, 2026.
That is roughly 80% of the register, which also covers people who have died or moved abroad. A national ID number is used across banking, healthcare and government services, and unlike a password it is not routinely reissued, which keeps it valuable to fraudsters long after the breach.
GRC Solutions counted 49 publicly disclosed incidents in October with at least 67.6 million confirmed records, and 17 of the 49 were in Japan. This report covers the largest incidents, separates confirmed figures from estimates, and closes with what small business websites should do about them.
⚠️ Important: 🚨 OCTOBER BREACH ALERT: Denmark's breach shows that legitimate access is an attack surface. The attackers misused a private company's authorized access, and according to the Danish Data Protection Agency the attack involved brute-forcing valid CPR numbers and extracting each matching entry. If you give partners, agencies or apps access to customer data, rate limits and alerts on unusual lookup volumes matter as much as passwords.
Denmark's CPR Register: 8.8 Million People Through One Company's Access
• Victim: Denmark's Central Person Register, the national civil registration system
• People affected: about 8.8 million, including current residents, people who moved abroad and deceased people
• Data exposed: names, addresses and CPR numbers; people registered with name and address protection were not affected (SecurityWeek)
• Method: misuse of a private Danish company's lawful access; the Danish Data Protection Agency described "some form of brute-forcing to enumerate valid CPR numbers"
• Timeline: activity during September; the CPR administration became aware on October 2 and announced the breach on October 5; the company's access was blocked and police opened an investigation
• Every partner, plugin or API client with access to customer data is a potential path to all of it. List them.
• Set per-client query limits and alert on volume spikes. Enumeration attacks look like a sudden flood of lookups from one account.
• Ask partners how they protect the credentials you issued them. Their weakest login becomes yours.
October 2026 Breaches at a Glance
| Organization | Scale | What was exposed | Status of the number |
|---|---|---|---|
| Sourcenext (Japan) | Up to 22.5M records | Emails, passwords, names, addresses, phone numbers | Maximum estimate |
| Skyticket (Japan) | About 14.64M records (includes duplicates) | Names, emails, phones, addresses; hashed passwords for about 4.13M | Company figure |
| Capcom (CAPCOM ID) | 11,774,247 records | Emails, last-login IPs, account activity data | Company-confirmed |
| Burger King Japan | About 11.18M records | Names, dates of birth, emails, phones, order history | Company-confirmed |
| Yakiniku King (Monogatari) | 10,788,963 member records | Names, emails, phones, membership numbers | Company-confirmed |
| Denmark CPR register | About 8.8M people | Names, addresses, national ID (CPR) numbers | Government-confirmed |
| Florida Dept. of Education | Nearly 5M aid applicants | Names, SSNs, dates of birth, addresses | State-confirmed |
| ETS / California Dept. of Education | Current and many former public school students (no total given) | Names, birth dates, addresses, disability and 504 status | State-confirmed |
| University of Copenhagen | 525,000 people | Names, CPR numbers, phones, emails (may have been exposed) | University-confirmed |
| Japan Airlines via Amadeus | About 92,000 customers | Booking details; passport numbers for about 2,000 | Airline-confirmed |
| Quest Diagnostics | Not disclosed | "Certain patient records" | Under investigation |
| ASOS | Not disclosed | Names and contact information | Under investigation |
Students and Patients: ETS, Florida and Quest Diagnostics
• System: the Florida Student Financial Aid website, which was taken offline
• People affected: nearly 5 million people who have applied for financial aid, according to The Record
• Data: names, addresses, phone numbers, genders, email addresses, Social Security numbers and dates of birth
• Timeline: the department became aware on October 19 and disclosed the breach on October 29; it has not described the attack
• System: Quanum LSM, which clients use to place lab test orders and look up results (Form 8-K)
• What Quest confirmed: it learned of unauthorized access to the system on October 21, 2026, and says "an unauthorized party accessed certain patient records"; the full scope is under investigation
• Not disclosed: how many patients are affected. TechCrunch notes this is Quest's second major breach in a decade, after 11.9 million patient records were exposed in 2019 through a third-party billing company
Japan's Consumer Breach Wave: Capcom, Burger King and More
• Burger King Japan: unauthorized access between October 2 and 7 to the server that manages members of its official app exposed about 11.18 million records, including names, dates of birth, gender, email addresses, phone numbers and order history
• Yakiniku King: operator Monogatari Corporation reported 10,788,963 member records leaked from its app's member system, almost its entire registered user base (GRC Solutions, Qatar Tribune)
• Skyticket: travel booking site operator Adventure, Inc. announced on October 9 that about 14.64 million customer records may have leaked, about 4.13 million of them with hashed login passwords (@IT)
• Sourcenext: the software company said on October 15 that up to 22,519,960 records, a maximum estimate, may have leaked from its member information system, including email addresses and passwords (ASCII.jp)
Vendor Chains, Test Data and Credentials That Never Expired
• Access window: airline IT provider Amadeus told JAL on October 23 that unauthorized access to its systems occurred between August 10, 2023 and September 23, 2026
• Affected: about 92,000 JAL customers; reservation codes, names and itineraries for about 90,000, plus email addresses, phone numbers, passport numbers and frequent flyer numbers for about 2,000 more (BleepingComputer)
• Wider impact: ANA, Asiana Airlines and Korean Air have also confirmed impact
• Confirmed: in a stock exchange filing, ASOS said hackers broke into a third-party platform hosting data it uses to communicate with customers, taking names and contact information. It also confirmed an "unauthorised customer notification" sent through its app. The hackers call themselves Xuanye Group
• Reported, not confirmed by ASOS: TechCrunch reports the data sat in a Snowflake instance (Snowflake says its own systems were not breached) and that the login was obtained by impersonating a trusted contact
• Unknown: how many customers are affected
• Hackers accessed one of the university's test environments holding personal data on 525,000 people; names, CPR numbers, phone numbers and email addresses may have been exposed (BleepingComputer)
• A later update added about 20,000 staff and students whose PIN codes were exposed, and the university restricted physical access to some campus locations while issuing new codes
• Developer hosting platform Zeabur is shutting down after its second breach in two months
• In the October 14–15 intrusion, an attacker used leaked internal credentials that Zeabur had stored in plaintext; the company said its admin tokens "had no expiry, had not been rotated since they were created in January 2024" (BleepingComputer)
• The attacker read data on 321,810 accounts and more than 3.2 million environment-variable records, where developers keep API keys and passwords
Check What Your Website Exposes
October's breaches ran through portals, test sites and leaked credentials. Run a free security scan on your live site (and your staging site) to check your SSL/TLS setup, eight security headers, and whether admin panels or sensitive files such as .env are publicly reachable.
Lessons for Small Business Websites
| Lesson | What to do this month | Does the free ScanComply scan help? |
|---|---|---|
| Trusted access gets abused (Denmark CPR) | List every partner, app and API key with access to customer data; add rate limits and volume alerts | No |
| Test sites need real security or fake data (Copenhagen) | Use masked or synthetic data in staging; never leave a staging site public without a login | Partly. Scan a staging URL for exposed admin panels and files such as .env |
| Credentials must expire (Zeabur) | Rotate admin tokens and API keys on a schedule and after any incident; never store them in plaintext | Partly. It checks whether .env and .git/config files are publicly downloadable |
| Vendors can be breached for months or years (Amadeus, ETS) | Ask vendors how they detect intrusions and how fast they must notify you; write it into the contract | No |
| Collect less (Burger King Japan, Skyticket) | Drop fields you don't need, such as date of birth, and delete dormant accounts | No |
| Your customer channels can be hijacked (ASOS) | Protect push-notification and email platforms with MFA and few admin seats | No |
| Get the basics right (all) | Valid HTTPS with modern TLS, plus security headers | Yes. It checks SSL/TLS and 8 security headers |
October's most instructive breaches were not technical marvels: a company's legitimate access to a national register, an SFTP account at a testing vendor, an airline IT provider with a three-year intrusion window, and admin tokens that never expired. Each one is a question about access: who has it, how much, and for how long.
Small businesses can ask the same questions of their own websites and vendors this month. Shorter-lived credentials, fewer stored fields and a current list of every partner with access will not make headlines, and that is the point.
Related reading: September 2026 breach report • August 2026 breach report • Fall 2026 website security checklist
Sources: BleepingComputer: Denmark CPR • GRC Solutions October summary • Help Net Security: Capcom • BleepingComputer: Burger King Japan • The Record: ETS • The Record: Florida • Quest Diagnostics 8-K • BleepingComputer: JAL and Amadeus • TechCrunch: ASOS • BleepingComputer: Zeabur
Disclaimer: Breach details summarize publicly reported information as of November 6, 2026 and may be revised as investigations continue. This article is general information, not legal advice.