The email you signed up to CAPCOM ID with, the time of your last login and the IP address you connected from are no longer only in Capcom's hands. On October 22, 2026, the company acknowledged the unauthorized access with an uncomfortable figure and a written apology: 11,774,247 records affected worldwide, according to the notice it published that same day.
CAPCOM ID is the single account used to sign in to the company's websites and to the online features of titles such as Resident Evil or Monster Hunter, and it can be linked to accounts on platforms such as PlayStation, Xbox or Steam. What was leaked is not a password. It is the trail that makes it possible to write an email that looks authentic, with the exact date you signed up and the date of your last login.
The detail that changes how the incident reads is not the big number. In 196 accounts, someone changed the password without the holder's permission, and that detail separates reading data from writing to accounts. Capcom has already reset those passwords, maintains that its games and services continue to operate normally and states that no card data was among what was exposed.
The trail left by every login
In its October 22 notice , Capcom separates three blocks, and that distinction explains why it speaks of records and not of people. The first is the email along with what the document calls system-specific identifiers: the sign-up date, the last login date, the number of logins and the IP of the last one.
The second block is 43 records with date of birth, sex, country or region and alias. The third is not data that was read, but an action: 196 passwords changed without the holder's permission. Capcom has not confirmed the compromise of the passwords chosen by customers, and payment data was not among what was affected.
The table orders the data by volume and by what each item allows whoever holds it to do, which is the question that really matters to a user.
| Data exposed |
Scope |
What it makes easier for an attacker |
| Email address |
11,774,247 records |
the list of recipients and the hook of the message |
| Session metadata (sign-up, last login, number of logins, IP) |
11,774,247 records |
an email with details that only an internal system would know |
| Date of birth, sex, country and alias |
43 records |
near-perfect impersonation in a small group |
| Customer-chosen passwords |
no signs of compromise |
nothing, as long as the holder does not reuse them |
| Card data |
not affected |
nothing |
The 11.7 million records do not equal 11.7 million people: the number measures affected records and may not represent that many distinct users, because the investigation into the scope remains open.
With those four metadata items, a stranger can write an email citing the sign-up date and the number of profile logins, and the recipient will read it as an internal communication. That is why the notice insists on not opening links or attachments in messages that impersonate Capcom or its partners.
The 196 accounts that weigh more than the figure
An unauthorized password change is the only indication in the notice that proves writing to accounts and not just reading. Reading a database makes it possible to prepare a deception; rewriting a credential means someone got to operate inside the account system, and there the leaked email stops being the most uncomfortable part of the matter.
Capcom has already reset those 196 passwords and keeps open the investigation into what else happened in those profiles. No group has claimed the attack, and the company says it has identified and closed the entry method without describing it. That leaves unanswered the question that matters most to an affected person: where the entry happened and how long the door was open.
The proportion invites downplaying it: 196 accounts out of 11.7 million records is 0.0017%. That percentage, however, is proof that the intrusion had the ability to modify data, even if only in a handful of cases, and that the account system was not protected against writing.
Four days between detection and the statement
The timeline of the notice is faster than that of most similar incidents. Capcom detected suspicious activity on October 19, 2026, and confirmed the unauthorized access that same day while blocking the entry; on the 20th it set up an internal response center and took the case to the Information Technology Security Oversight Committee, its external advisory body; on the 21st it reported it to the Osaka Prefectural Police and to Japan's Personal Information Protection Commission; on the 22nd it published the statement and opened support channels by region.
The contrast with the company's previous episode helps gauge the change. Six years ago, a ransomware attack by the Ragnar Locker group encrypted data on its servers and may have affected up to 350,000 customers, partners and employees. Then there was a group with a name and an extortion; now there is a silent access that no one has claimed.
Capcom was not the only Japanese company with a scare this week. GMO Internet shut down the Onamae Desktop Cloud servers after finding foreign programs on customer machines, with 26,739 devices possibly exposed, and it too went to the police on October 22.
For anyone with an account, the notice leaves one concrete instruction and quite a few unanswered questions. These checks are the ones that really change something, ordered by what prevents the most harm with the least effort.
- Change the password to one you do not use anywhere else and store it in a manager, because reuse turns one leak into five.
- Enable two-factor authentication with an authenticator app; Capcom suggests Google Authenticator or Microsoft Authenticator.
- Go to cid.capcom.com by typing the address by hand and review the profile data and linked platform accounts there.
- Treat as suspicious any email announcing a password change you did not request or rushing you to click.
- If you need help, use the channels in the notice (the Japanese toll-free line 0120-801-271 and the forms by region) instead of a contact that arrives by message.
Two-factor authentication deserves a separate comment, because it is the only measure on the list that still protects when the password is already circulating on a forum. With an app code on your phone, whoever has the email and the IP of the last login is still locked out of the account, and that is exactly the scenario this breach paints.
It is also worth looking at linked accounts, because CAPCOM ID acts as a bridge to platform stores and services. If someone gets into the Capcom profile, they see which external accounts hang from it and which email they are associated with, a map that saves work for anyone preparing a deception with the data in the table.
Entertainment is the cheapest gateway for phishing
A video game account is not protected like a bank account, and that asymmetry is exactly what those who set up a fraud are looking for. No one knowingly reuses their financial institution's password; by contrast, millions of players sign in with the same password on launch portals, forums and services for their favorite franchises, and an email that says it comes from Capcom is opened with less suspicion than one from the bank.
What the industry should be required to do is not a technological revolution either. Notifying the user before the leak hits the press, offering two-factor authentication enabled by default from the first sign-up and explaining the attack method once it is closed are three cheap decisions that remain optional across much of the entertainment sector.
Until that happens, the malware used to prepare these strikes keeps getting more sophisticated: Lazarus now shields its own with post-quantum cryptography. The part that depends on the player is still the cheapest to fix, and also the only part that can be resolved this very afternoon.