Technology & AI
Capcom Confirms Data Breach Affecting 11.7 Million CAPCOM ID Accounts Globally
A cyberattack on Capcom's online membership service exposed email addresses and system identifiers for millions of users, prompting warnings about phishing attempts.
Share this article
THE PRIMARY BRIEF
- 01 · The primary finding
Capcom confirmed a data breach on October 22, 2026, affecting 11,774,247 CAPCOM ID accounts globally, exposing email addresses and system-specific identifiers.
- 02 · The primary evidence
Capcom's official announcement detailed the compromise of email addresses and system identifiers, with 43 accounts having additional personal data exposed and 196 accounts experiencing unauthorized password changes.
- 03 · Why it matters
The exposed email addresses increase the risk of phishing attacks for millions of users, potentially leading to further compromise of personal information.
Capcom officially confirmed a data breach on October 22, 2026, impacting 11,774,247 CAPCOM ID accounts globally. The breach exposed customer email addresses and system-specific identifier information, raising concerns for users worldwide.
This incident matters to readers because their exposed email addresses could be used in phishing campaigns, where malicious actors attempt to trick users into revealing sensitive information or installing malware. Affected users are advised to be vigilant against fraudulent communications that may impersonate Capcom.
What the records show
Capcom's disclosure on October 22, 2026, stated that 11,774,247 CAPCOM ID accounts had their email addresses and system-specific identifiers compromised. These identifiers included account creation dates, last login times, the total number of logins, and the IP address used during the last login. For a smaller group of 43 accounts, additional personal details were exposed: date of birth, gender, country or region, and nickname. While 196 CAPCOM ID accounts experienced unauthorized password changes, Capcom maintained that customer-set passwords were not leaked. The company also confirmed that no credit card information was affected in the breach.
The timeline
The sequence of events began on October 19, 2026, when Capcom detected suspicious activity indicating potential unauthorized access to CAPCOM ID. The company immediately initiated blocking measures and launched an investigation into the cause and scope of the incident. By October 20, an internal task force was established to coordinate the response. Capcom reported the incident to the Osaka Prefectural Police and Japan's Personal Information Protection Commission on October 21, 2026. The official public disclosure was made on October 22, 2026.
What changed and for whom
Following the breach, Capcom implemented emergency response measures and identified the attack method. The company confirmed that services utilizing CAPCOM ID remain operational, allowing players to continue accessing their games. For the 196 accounts where passwords were changed without authorization, Capcom has already reset those passwords. The company stated it is continuing to investigate the extent of any further impact.
What the subject has said publicly
Capcom issued a public apology for the complications and concern caused to its customers and stakeholders. The company stated it would notify affected customers about the incident. Capcom advised users to be extremely cautious regarding potential phishing attempts, urging them to avoid clicking suspicious links or opening attachments in unexpected emails. The company recommended that users access their accounts directly through official channels to verify any information.
What we could not confirm
Capcom's public statements did not explain the technical details of how the attackers gained initial access to its systems. The specific method attackers used to change passwords for 196 accounts without reportedly leaking customer-set passwords was not detailed. The identity of the third party responsible for the unauthorized access remains unconfirmed in the provided information.
SHOW YOUR WORK