# Capcom data breach: what 11.77M CAPCOM ID records means

> Capcom data breach: 11,774,247 CAPCOM ID email records, 196 password changes, 19 profiles read. What was and was not exposed, and what to do this week.

Canonical: https://red.run.cloud/learn/capcom-id-breach-11-77-million-accounts · By Timothy Lindblom · Published 2026-11-02 · Updated 2026-11-02

Capcom said on 22 October 2026 that someone gained unauthorized access to CAPCOM ID and reached 11,774,247 records of email addresses and system identifiers. Passwords were changed on 196 accounts, and on 23 October Capcom said 19 of those also had profile data read. Credit card data was not included. Change reused passwords and treat Capcom-themed email with suspicion.

| Fact | Detail | Source |
|---|---|---|
| Service | CAPCOM ID, Capcom's online membership login | [Capcom notice](https://www.capcom.co.jp/ir/english/news/html/e261022.html) |
| Detected | 19 October 2026, unauthorized access confirmed the same day | Capcom notice |
| Disclosed | 22 October 2026; updated 23 October 2026 | [Capcom update](https://www.capcom.co.jp/ir/english/news/html/e261023.html) |
| Widest set | 11,774,247 records of email addresses and system identifiers (IP addresses, login timestamps, account creation dates) | Capcom notice |
| Profile fields | 43 records of date of birth, gender, country or region and nickname | Capcom notice |
| Password changes | 196 accounts changed without authorization; passwords already reset by Capcom | Capcom notice |
| Store data read | 19 of the 196 (Japan only): name, phonetic name, phone, postal code, address, gender, date of birth, purchase history, inquiry history, saved address book | Capcom update |
| Not included | Credit card information | Both notices |
| Cause | Capcom says it identified and addressed the attack method. It has not published what it was | Capcom notice |
| Checked | 2 November 2026 | this page |

## What did Capcom say happened, and when?

Capcom detected suspicious activity on 19 October 2026 and confirmed unauthorized access the same day. It set up an internal incident response headquarters on 20 October and reported to its external advisory body, the Information Technology Security Oversight Committee. It notified the authorities on 21 October and published its notice on 22 October. [BleepingComputer](https://www.bleepingcomputer.com/news/security/capcom-confirms-data-breach-affecting-117-million-accounts/) covered the first notice.

<figure class="ln-figure">
<svg viewBox="0 0 720 200" role="img" xmlns="http://www.w3.org/2000/svg" font-family="Geist, sans-serif">
<title>Timeline of the CAPCOM ID incident from 19 to 23 October 2026</title>
<rect x="0" y="0" width="720" height="200" fill="#FFF1EF"/>
<line x1="60" y1="90" x2="660" y2="90" stroke="#EAD3CF" stroke-width="3"/>
<circle cx="60" cy="90" r="9" fill="#C70500"/>
<circle cx="195" cy="90" r="9" fill="#C70500"/>
<circle cx="330" cy="90" r="9" fill="#C70500"/>
<circle cx="465" cy="90" r="9" fill="#B00500"/>
<circle cx="600" cy="90" r="9" fill="#B00500"/>
<text x="60" y="62" text-anchor="middle" font-size="15" font-weight="600" fill="#1A0F0F">19 Oct</text>
<text x="195" y="62" text-anchor="middle" font-size="15" font-weight="600" fill="#1A0F0F">20 Oct</text>
<text x="330" y="62" text-anchor="middle" font-size="15" font-weight="600" fill="#1A0F0F">21 Oct</text>
<text x="465" y="62" text-anchor="middle" font-size="15" font-weight="600" fill="#1A0F0F">22 Oct</text>
<text x="600" y="62" text-anchor="middle" font-size="15" font-weight="600" fill="#1A0F0F">23 Oct</text>
<text x="60" y="124" text-anchor="middle" font-size="13" fill="#655553">Suspicious</text>
<text x="60" y="142" text-anchor="middle" font-size="13" fill="#655553">activity found,</text>
<text x="60" y="160" text-anchor="middle" font-size="13" fill="#655553">access confirmed</text>
<text x="195" y="124" text-anchor="middle" font-size="13" fill="#655553">Response HQ set up,</text>
<text x="195" y="142" text-anchor="middle" font-size="13" fill="#655553">advisory body</text>
<text x="195" y="160" text-anchor="middle" font-size="13" fill="#655553">informed</text>
<text x="330" y="124" text-anchor="middle" font-size="13" fill="#655553">Authorities</text>
<text x="330" y="142" text-anchor="middle" font-size="13" fill="#655553">notified</text>
<text x="330" y="160" text-anchor="middle" font-size="13" fill="#655553"> </text>
<text x="465" y="124" text-anchor="middle" font-size="13" fill="#655553">Public notice:</text>
<text x="465" y="142" text-anchor="middle" font-size="13" fill="#655553">11,774,247 records,</text>
<text x="465" y="160" text-anchor="middle" font-size="13" fill="#655553">196 accounts</text>
<text x="600" y="124" text-anchor="middle" font-size="13" fill="#655553">Update: 19 of the 196</text>
<text x="600" y="142" text-anchor="middle" font-size="13" fill="#655553">had profile data</text>
<text x="600" y="160" text-anchor="middle" font-size="13" fill="#655553">read</text>
<text x="360" y="188" text-anchor="middle" font-size="12" fill="#655553">Source: Capcom notices of 22 and 23 October 2026</text>
</svg>
<figcaption>The incident as Capcom dated it. All five dates come from Capcom's own notices.</figcaption>
</figure>

Capcom says it has identified and addressed the attack method. It has not said what the method was, which matters for the unknowns section below.

## How many people are really affected?

The headline number is the widest of four. Capcom's notices describe four different sets, and they get blurred when the story is repeated as "11.77 million accounts hacked". Capcom's own wording for the largest figure is records, not accounts.

| Set | Count | What it contains | What it means for you |
|---|---|---|---|
| Email and identifier records | 11,774,247 | Email address, system-specific identifiers, IP addresses, login timestamps, account creation dates | Your address can be used to target you with messages. No password is listed for this set |
| Profile records | 43 | Date of birth, gender, country or region, nickname | A very small group. Capcom says it will begin contacting affected customers |
| Passwords changed without authorization | 196 accounts | A new password set by someone else; Capcom has reset these | An attacker could sign in to these accounts. Capcom says the original passwords were not compromised |
| Store data accessed | 19 accounts, Japan only | Name, address, phone, date of birth, purchase and inquiry history, address book | The only group where personal and purchase data was read |

The 177 other accounts in the 196 had no information compromised, according to the [23 October update](https://www.capcom.co.jp/ir/english/news/html/e261023.html). That update is why a story written on 22 October can now be out of date.

Capcom warned that the information could be misused to send fraudulent emails or other communications impersonating Capcom. That risk is the practical one for most of the 11.77 million, because an email address plus the fact that you use Capcom is enough to write a convincing message.

## What was not exposed?

Capcom states plainly that [credit card information was not included](https://www.capcom.co.jp/ir/english/news/html/e261022.html) in the affected information. Its notice also does not list passwords, password hashes or payment details among the 11,774,247 records. It describes only the 196 password changes, and says the original passwords on those accounts were not compromised.

Absence from a notice is not proof of absence from the incident. We can say what Capcom said on 22 and 23 October. We cannot say what its logs contain beyond that.

## Do I need to do anything if I have a CAPCOM ID?

Yes, a short list. None of it needs you to know whether you are in the 11.77 million.

- [ ] Change the CAPCOM ID password if you use it anywhere else. Reuse is what turns one breach into several.
- [ ] Use a long, unique password. The [NCSC](https://www.ncsc.gov.uk/collection/top-tips-for-staying-secure-online/three-random-words) recommends three random words for length and a password manager to remember them.
- [ ] Check the password against [Pwned Passwords](https://haveibeenpwned.com/Passwords), which uses a method that sends only part of a hash, not the password.
- [ ] Turn on [breach alerts](https://haveibeenpwned.com/NotifyMe) for your email address. The service is free and verifies ownership with a link sent to your inbox.
- [ ] Look at the account's sign-in history and linked details if the service shows them. Remove saved addresses you do not use.
- [ ] If you are in Japan and see unfamiliar orders, contact the Capcom hotline listed in the [notice](https://www.capcom.co.jp/ir/english/news/html/e261022.html). Capcom gives 0120-801-271, 10 a.m. to 8 p.m. JST. Outside Japan it points to online support forms.

If Capcom emails you, it will be because you are in a specific set. Capcom said in the notice that it will begin contacting affected customers. No email today means nothing either way.

<div class="ln-selftest">
<h3>Am I affected? Where you stand right now</h3>
<p>Only Capcom can say which set an account is in. A breach list or a search from outside can point to exposure of an address. It cannot show what is in Capcom's records.</p>
<ol>
<li><span class="ln-state ln-state-detected">Detected</span> <strong>Capcom has contacted you, or the account's password was changed and you did not do it.</strong> Treat the account as exposed. Sign in only through the official site, set a new unique password, and review the profile, address book and order history.</li>
<li><span class="ln-state ln-state-unknown">Unknown</span> <strong>You have or had a CAPCOM ID and have heard nothing.</strong> This is the common case, and with 11,774,247 records in scope it is a likely one. Assume your email address is exposed, change any reused password, and expect Capcom-themed messages.</li>
<li><span class="ln-state ln-state-confirmed">Confirmed by owner evidence</span> <strong>You hold a Capcom message sent from an address you verified, or an account log showing the change.</strong> The record is yours to keep. Note the date, which set Capcom puts you in, and the steps you took after.</li>
</ol>
<p>No lookup, ours included, moves you from "unknown" to "confirmed". Capcom's own notice to you does.</p>
</div>

## How do I spot a fake Capcom message?

With an email list this size, expect copies. [CISA](https://www.cisa.gov/secure-our-world/recognize-and-report-phishing) lists the signs: urgent or emotional language, requests for personal or financial information, shortened links, and addresses or links that are one letter off. Its advice for a message that might be real is to avoid the embedded links, go to the company's site by typing the address yourself, and confirm through a separate channel.

For this incident, three details help:

- Capcom has said it has not exposed credit card information, so a message asking you to "confirm your card" fits no part of the notice.
- Capcom has said it will contact affected customers. A message that arrives claiming to be that contact should still be checked on the official site, not through its own links.
- A message that says your account is locked, and sends you to a login page, is the pattern a password change on 196 accounts makes easy to imitate.

## What do we not know yet?

As of 2 November 2026, four things are open, and Capcom has published nothing on the incident since its 23 October update.

| Open question | What Capcom has said | Why it matters |
|---|---|---|
| How the attacker got in | "Identified and addressed the attack method", no detail | Decides whether other Capcom services were reachable the same way |
| Whether reused passwords played a part | Nothing | Determines whether the 196 were guessed, reused or reset another way |
| Whether password hashes were read | Not listed in the notices | Changes how urgent a password change is for the other 11.77 million |
| Whether the counts will change | One update in the first two days | The 23 October update already narrowed the picture once |

Re-read the Capcom [press release index](https://www.capcom.co.jp/ir/english/news/) before acting on any figure here. It listed both notices, and nothing newer on the incident, at our check on 2 November 2026.

## Is this the same as Capcom's 2020 breach?

No source links them. Capcom's [November 2020 notice](https://www.capcom.co.jp/ir/english/news/html/e201116.html) described a ransomware attack by a group calling itself Ragnar Locker, with about 350,000 items of personal information potentially affected and no credit card data among them. The 2026 notices describe unauthorized access to a membership service and do not name a group, a ransomware demand or a cause. Treat them as two incidents.

## What should a site with its own logins take from this?

The pattern in the notices is worth reading even if you never play a game. Someone changed 196 passwords on a membership service. The service reset them, narrowed the exposure to 19 accounts a day later, and gave the owner a hotline number. If your site has accounts, ask which of those steps you could do. If you ever have to tell your own users, there is a [template for emailing customers about a breach](/learn/email-customers-about-a-security-breach-template).

The [OWASP credential stuffing cheat sheet](https://cheatsheetseries.owasp.org/cheatsheets/Credential_Stuffing_Prevention_Cheat_Sheet.html) defines credential stuffing as testing username and password pairs from one site's breach against another. Capcom has not said that is what happened here. The same controls limit the damage from account takeover in general, though MFA alone does not help once [a stolen session cookie](/learn/stolen-session-cookie-bypasses-mfa) is replayed.

| Control | What it does | Source |
|---|---|---|
| Multi-factor authentication | OWASP calls it "by far the best defense against the majority of password-related attacks" | [OWASP](https://cheatsheetseries.owasp.org/cheatsheets/Credential_Stuffing_Prevention_Cheat_Sheet.html) |
| Rate limiting and IP checks | Slows repeated login attempts, including slow, steady ones | OWASP |
| Breached-password checks | Rejects new passwords found in known breach data, using a service such as Pwned Passwords | OWASP, [HIBP](https://haveibeenpwned.com/Passwords) |
| Login and password-change notices | Emails the account owner after a successful sign-in or change, and shows previous login details | OWASP |
| A phone line and a plan | Gives owners a way to report a change they did not make, as Capcom listed | [Capcom notice](https://www.capcom.co.jp/ir/english/news/html/e261022.html) |

If you run a site and want to know what an outside view shows, the free scan reads the stack your site serves and matches each version to known vulnerabilities. It also checks TLS, cookie flags and exposed `.env` or `.git` files. It is a lookup. It cannot see whether your accounts are being tried with reused passwords, and our [note on what an external scan cannot prove](/learn/what-an-external-website-scan-cant-prove) covers the rest. If an incident has already happened, the [step-by-step response for a live incident](/learn/website-incident-response-playbook) and the [guide to rotating secrets](/learn/rotate-secrets-after-a-breach-guide) are the next steps.

## Where does this sit among October's incidents?

Capcom's notice arrived the same week as several unrelated disclosures, including [another Japanese app with 11 million member records](/learn/burger-king-japan-app-breach-11-million-records) and [a rogue push alert sent through a retailer's app](/learn/asos-breach-social-engineering-push-notification). The rest are in [our other breach write-ups](/learn/topics/breaches). They are different problems with different fixes, and none is linked to this one by a source. The [running list of October cases](/learn/october-2026-security-meltdown-tracker) keeps the verified list, and the [2026 incident timeline](/learn/2026-cyber-incidents-timeline) shows how the weeks line up.

## Questions people ask

### Was my Capcom account part of the breach?

Possibly. Capcom said 11,774,247 records of email addresses and system identifiers were affected, which is a very large share of all CAPCOM ID accounts. Capcom said it will begin contacting affected customers, so no email yet does not mean you were missed. Treat your email address as exposed and act on that.

### Were passwords stolen in the Capcom data breach?

Capcom said credit card information was not included, and that the original passwords on the 196 accounts with unauthorized password changes were not compromised. Its notice does not say passwords were part of the 11.77 million records. It also has not said how the attacker got in.

### What is the difference between 11.77 million, 196 and 19?

The 11.77 million figure is records of email addresses and system identifiers. The 196 are accounts whose passwords were changed without authorization. On 23 October Capcom said 19 of those 196 also had personal and store data accessed, and the other 177 had none. The three numbers describe three different levels of exposure.

### Do I need to change my Capcom password?

Capcom reset the passwords on the 196 affected accounts itself. Everyone else with a CAPCOM ID should still change the password if it is reused anywhere, and turn on any extra sign-in step the service offers. A long unique password from a password manager costs nothing and limits the damage from any later breach.

### How do I know if an email from Capcom is real?

Do not use the links in it. Type the address of the Capcom site yourself, or use the app, and check your account there. Capcom said fraudulent messages impersonating it are a risk, and asked customers not to click URLs or open attachments in suspicious ones.

### Is the Capcom breach the same as the 2020 one?

No source links them. The 2020 incident was a ransomware attack that Capcom announced on 16 November 2020. The 2026 notice describes unauthorized access to CAPCOM ID and does not name a ransomware group or a cause.


## Sources

1. [Capcom: Notice and Apology Regarding Customer Information Affected Through Unauthorized Access (22 October 2026)](https://www.capcom.co.jp/ir/english/news/html/e261022.html): The original notice. Source of the dates, the 11,774,247, 43 and 196 figures and the statement that credit card data was not included.
2. [Capcom: Update to Notice and Apology Regarding Customer Information Affected Through Unauthorized Access (23 October 2026)](https://www.capcom.co.jp/ir/english/news/html/e261023.html): Narrows the 196 accounts: 19 had store page data accessed, the other 177 had none. Lists the profile fields.
3. [Capcom: press release index, October 2026](https://www.capcom.co.jp/ir/english/news/): Shows both notices and no later one on the incident. Checked 2 November 2026.
4. [BleepingComputer: Capcom confirms data breach affecting 11.7 million accounts (22 October 2026)](https://www.bleepingcomputer.com/news/security/capcom-confirms-data-breach-affecting-117-million-accounts/): Press coverage of the first notice. Secondary source, used only where it matches Capcom's page.
5. [Capcom: Notice on a data security incident (16 November 2020)](https://www.capcom.co.jp/ir/english/news/html/e201116.html): The earlier, separate ransomware incident. Capcom has not linked the two.
6. [Have I Been Pwned: Notify Me](https://haveibeenpwned.com/NotifyMe): Free alerts when an email address appears in a new breach. Ownership is verified by a link sent to the inbox.
7. [Have I Been Pwned: breach list](https://haveibeenpwned.com/PwnedWebsites): At our check on 24 October 2026 the list showed no Capcom entry.
8. [Have I Been Pwned: Pwned Passwords](https://haveibeenpwned.com/Passwords): Checks a password against known breaches without sending the password itself.
9. [CISA: Recognize and report phishing](https://www.cisa.gov/secure-our-world/recognize-and-report-phishing): Signs of a phishing message and what to do with one.
10. [OWASP Credential Stuffing Prevention Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/Credential_Stuffing_Prevention_Cheat_Sheet.html): Defences for site operators: MFA, rate limiting, breached-password checks, login notifications.
11. [NCSC (UK): Three random words](https://www.ncsc.gov.uk/collection/top-tips-for-staying-secure-online/three-random-words): Password length and password manager advice.
