---
title: "Capcom: 11.77M CAPCOM ID emails leaked, warns of phishing"
date: "2026-10-23"
author: "Ahsan Luqman"
canonical_url: "https://aliasfleet.com/blog/capcom-data-breach"
tags: ["Data Breaches", "Privacy", "Email Aliases", "Gaming"]
description: "Capcom confirmed 11.77 million CAPCOM ID emails leaked and warned that forgers will impersonate the company. The leaked login metadata makes them convincing."
---

# Capcom: 11.77M CAPCOM ID emails leaked, warns of phishing

Capcom confirmed 11.77 million CAPCOM ID emails leaked and warned that forgers will impersonate the company. The leaked login metadata makes them convincing.

The October 2026 Capcom CAPCOM ID data breach is a data breach disclosed by Capcom on 22 October 2026, in which 11,774,247 email addresses associated with CAPCOM ID accounts were leaked together with login metadata. CAPCOM ID is the unified account required to use Capcom's web services and to play some of its games online. Capcom confirmed the leak in its own investor-relations notice of 22 October 2026 and warned that the leaked information could be misused to send fraudulent messages impersonating Capcom or related parties. No credit card information was included in the leaked data, and Capcom stated that services using CAPCOM ID continue to operate and that gameplay is unaffected.

## Capcom CAPCOM ID disclosure chronology

On 19 October 2026, suspicious access traces were found in the CAPCOM ID system, the access was blocked, and the intrusion was confirmed on the same day. On 20 October 2026, Capcom established an internal response headquarters, confirmed the leak, and confirmed the unauthorised password changes. On 21 October 2026, Capcom reported the incident to the Osaka Prefectural Police and to Japan's Personal Information Protection Commission. On 22 October 2026, Capcom published its disclosure in an investor-relations notice, available in [Japanese](https://www.capcom.co.jp/ir/news/html/261022.html) and in [English](http://www.capcom.co.jp/ir/english/news/html/e261022.html), and [Reuters JP](https://www.reuters.com/jp/economy/2UGI7DZNMJNUZJWFDMD6BJWDIU-2026-10-22/) and [4Gamer](https://www.4gamer.net/games/999/G999905/20261022034/) restated the company figures on the same day.

## CAPCOM ID leaked record fields

The figures stated by Capcom are a worldwide total of 11,774,247 records, each pairing an email address with system identifiers: the account creation date and time, the last-login date and time, the login count, and the client IP address used at last login. Capcom describes the leak as confirmed, not as an estimate. Within that total, a subset of 43 records also included date of birth, gender, country or region, and nickname. In a further 196 accounts, login passwords were changed without authorisation, and Capcom states that it has not confirmed any leak of the passwords customers set themselves and that the 196 accounts have already been reset. No credit card information was present in the leaked data, and Capcom states that the scope of impact is still under investigation.

| Confirmed by Capcom | Not yet confirmed |
| :--- | :--- |
| The leak itself, announced on 22 October 2026, at 11,774,247 records worldwide | The attack method, which Capcom says it identified and addressed but about which it disclosed no technical detail |
| The identifiers beside each email: account creation date and time, last-login date and time, login count, and client IP address at last login | Whether the dataset is circulating, being sold, or has been used for anything beyond the 196 password changes |
| The 43-record subset: date of birth, gender, country or region, and nickname | Whether the 11.77 million count grows as the investigation continues |
| The 196 accounts: passwords changed without authorisation, all reset, with user-set passwords not confirmed leaked | What the attacker did inside the 196 accounts |
| No credit card data, services continuing to run, and affected customers to be notified individually | Whether those individual notifications have started arriving |

## CAPCOM ID login metadata and impersonation mechanism

The email addresses are the largest part of the leak, and the identifiers beside each address are the material that makes a forged message persuasive. A message quoting the account creation date and time, the last-login date and time, the login count, and the client IP address used at last login would match the account holder's own records, because those fields are present in the leaked records. A recipient checking the quoted details against personal records would find them correct, and the match would come from the leaked file rather than from any connection between the sender and Capcom. For the 43 people in the subset, the additional fields of date of birth, gender, country or region, and nickname provide further material for personalising a lure and for working through account-recovery questions on other services.

## Capcom impersonation warning in the October 2026 notice

Capcom placed the impersonation warning in the body of its own notice, stating that the leaked information could be misused to send fraudulent messages impersonating Capcom or related parties and that customers should not access URLs or open attachments in suspicious mail. Capcom also stated that it will notify affected customers individually, so a forged copy of that notification is a likely next step, and the genuine notification and a forgery quoting the same incident would arrive with the same context. The distinction between the two rests on the destination reached, not on the content read: Capcom's own site or support pages, reached by typing the address directly, rather than a page reached through a link in an email about the breach.

<Callout type="warning" title="Capcom's own advice">
Capcom states that customers may receive fraudulent messages impersonating the company or its partners, and asks recipients not to access the URLs or open the attachments in any suspicious mail. Capcom will notify affected customers individually, so forged copies of that notification are the most likely next move. Capcom's own advice directs recipients to reach the company's site directly rather than through a link in an email about the breach.
</Callout>

## Reported measures for affected CAPCOM ID holders

Capcom's published advice for recipients of suspicious mail is not to access URLs or open attachments in such mail, and to reach Capcom's site directly rather than through a link. Published breach-response guidance describes a password change for the CAPCOM ID account, with the replacement password unique to Capcom, and two-factor authentication on the email account behind the CAPCOM ID account, on the grounds that a leaked address combined with leaked login history is the raw material of account-recovery attacks. The same guidance describes checking [Have I Been Pwned](https://haveibeenpwned.com/) once the incident is added there, and working through the [breach-response order of operations](https://www.aliasfleet.com/blog/what-to-do-when-your-email-is-in-a-data-breach). It also describes not reusing the password used at Capcom on any other service, and changing it on any other service where it matches, because credential stuffing pairs a leaked email with passwords taken from other breaches. Published guidance further describes expecting messages that quote real account details, since anyone reading a creation date, a last login, or an IP address back to an account holder is demonstrating possession of the leaked file rather than membership of a security team.

## Alias use across gaming accounts

Gaming accounts are registrations that are commonly created for one game, using an address that is also used elsewhere, and then left in place for years. Under an alias arrangement, a unique [email alias](https://www.aliasfleet.com/blog/what-is-an-email-alias) is assigned to each gaming service and forwards to the account holder's real inbox. [AliasFleet](https://aliasfleet.com) provides one forwarding address per site on that model. Mail arriving on an address used only for Capcom is then attributable to either Capcom or to holders of the leaked data, and a message on that address asking the holder to confirm details already held by Capcom identifies itself as a forgery, since Capcom already holds the alias on file and would not need it handed back. Shutting down the Capcom-only alias removes the delivery route for forgeries aimed at that account, while the real inbox receives nothing further on that address. The same arrangement identifies the source of a leak: a message arriving on an address used at exactly one service indicates the service from which it escaped, which is the [leak-tracing mechanism](https://www.aliasfleet.com/blog/which-website-leaked-my-email) described by AliasFleet.

## Capcom 2020 ransomware incident

The October 2026 CAPCOM ID leak is Capcom's second major breach in six years, and the two incidents affected different systems. In November 2020, Capcom was hit by a customised ransomware attack on its corporate network, not on CAPCOM ID. In its third update, in January 2021, Capcom verified the personal data of 16,415 people as compromised and put the potential maximum at around 390,000 customers, business partners, and others, with names, addresses, emails, and dates of birth among the data at risk ([Capcom's update](http://www.capcom.co.jp/ir/english/news/html/e210112.html)). [Polygon's reporting at the time](https://www.polygon.com/2020/11/16/21569504/capcom-leak-ransomware-resident-evil-village-release-dates-monster-hunter-stories-2-nintendo-switch/) covered what was leaked, including corporate secrets and source code. The terabyte figure associated with that attack was the attackers' own claim: their ransom note stated that roughly a terabyte of data had been exfiltrated, as [BleepingComputer reported at the time](https://www.bleepingcomputer.com/news/security/the-week-in-ransomware-november-6th-2020-video-games-and-liquor/amp/). Capcom states that it has identified and addressed the attack method in the 2026 incident, but has disclosed no technical detail about it.

## Unresolved questions in the CAPCOM ID investigation

Capcom's notice closes with a promise to update its official site as new facts emerge, and several facts remain unshared. No technical detail about the attack method has been disclosed, so no other company holding the same kind of account data can learn from it. Nothing has been confirmed about whether the 11.77 million records are circulating or sitting quiet, beyond the 196 password changes, and nothing has been confirmed about whether the count grows as the investigation continues. At the time of the notice, no impersonation wave of the kind Capcom warned about had been reported, and whether the individual notifications to affected customers have started arriving also remains unconfirmed.
