Capcom ID: 11.77 million records exposed, but what did attackers actually change?
Capcom confirmed unauthorized access to its CAPCOM ID service in October 2026, affecting 11,774,247 email and account-metadata records. It separately identified 196 accounts with unauthorized password changes. The company did not report theft of customers' original passwords.
Background
CAPCOM ID is the company's unified account service used across web services and online gaming. Account metadata and email addresses can have value for targeted impersonation even when payment-card information and original account passwords are not reported exposed.
Capcom's 22 October 2026 disclosure supplies a day-by-day detection and response account but does not publicly explain the exact exploitation mechanism.
Documented CAPCOM ID impact and response
What actually happened
On 19 October 2026, Capcom detected suspicious activity involving CAPCOM ID, blocked access and confirmed unauthorized access the same day.
On 20 October, it established an incident-response headquarters and confirmed affected customer information and unauthorized password changes. On 21 October, it reported the incident to Osaka Prefectural Police and Japan's Personal Information Protection Commission.
As of its 22 October disclosure, Capcom identified 11,774,247 affected records of email addresses and system-specific identifiers, 43 records additionally involving demographic and nickname fields, and 196 accounts whose passwords were changed without authorization. It said original customer-set passwords were not confirmed compromised and payment-card information was not included.
Root cause
- Capcom confirmed unauthorized third-party access to CAPCOM ID and said it identified and addressed the attack method.
- The company did not publicly specify the entry point, vulnerability, credential abuse or exploit chain in its 22 October statement; no one mechanism can be asserted.
Timeline
Detection
Capcom detected suspicious activity on 19 October 2026 and confirmed unauthorized access the same day.
What to monitor for in your own environment
Unexpected access to large volumes of member data
Application access and database audit logsUnusual password-change volume or patterns
Identity and account-management logsUnfamiliar client locations or automated sessions
Authentication telemetryContainment, eradication & recovery
Containment
19 October 2026- Capcom immediately blocked suspicious access and began emergency measures.
Eradication
19–22 October 2026- Capcom said it identified and addressed the attack method, without disclosing the technical mechanism.
- It reset passwords on the 196 accounts with unauthorized changes.
Recovery
From 22 October 2026- CAPCOM ID services remained available, according to the company.
- Capcom planned individual customer notifications and dedicated support while continuing its investigation.
Security control analysis
Third-party unauthorized access occurred; the specific failed technical control was not disclosed.
Capcom reported detection and blocking on 19 October.
196 account passwords were changed without authorization.
Capcom had not confirmed original customer-password compromise; this is not proof of a particular protective control.
Controls that would have prevented or limited this
Could reduce the scale of unauthorized data retrieval and trigger early investigation.
Makes unauthorized password changes harder and easier to detect.
Helps investigate account-data exposure and integrity events.
Blast radius
Confirmed affected information
- 11,774,247 email and system-identifier records.
- 43 of those records included date of birth, gender, country/region and nickname.
- 196 accounts experienced unauthorized password changes; those passwords were reset.
Not confirmed or excluded
- Original customer-set password theft was not confirmed.
- Payment-card information was not included in the disclosed affected data.
- The initial attack technique and full duration of unauthorized access were not publicly detailed.
Reported affected categories
What they got right
Capcom reported same-day detection and blocking on 19 October.
The company disclosed distinct categories and counts instead of describing every record as a password compromise.
It reported to police and privacy authorities and said CAPCOM ID services remained available.
Why this keeps happening
Large identity services aggregate email addresses and behavioral metadata useful for social engineering.
Unauthorized access can affect both confidentiality and account integrity without evidence of original password theft.
Public disclosures often describe impact before the full technical entry point is released.
Lessons for your own environment
- Exposure is not password theft
Disclose what is known without conflating metadata exposure and compromise of customer-set passwords.
- Account integrity matters
Unauthorized password changes are a separate risk from data confidentiality.
- Publish precise counts
A clear breakdown helps customers understand what was and was not affected.
CISO & board lessons
- Require incident dashboards to separate data disclosure, account takeover and unauthorized account modifications.
- Review alerting on both bulk reads and sensitive identity changes.
- Preserve clarity in customer notifications when technical root cause remains undisclosed.
Action plan
First 24 hours
- Block confirmed unauthorized access, preserve identity and application logs, and identify affected data classes.
- Protect accounts with confirmed unauthorized changes.
First 7 days
- Validate the impact scope and notify regulators and affected users as required.
- Review anomalous password changes and account access.
First 30 days
- Verify remediation of the entry path once established.
- Improve bulk-access and account-integrity monitoring.
Could this happen in your organization?
- Can we separately measure data exposure and unauthorized account changes?
- Do password-change anomalies generate timely alerts?
- Can we explain precisely what is not known without asserting it was safe?
If this happened to you: what to ask, and what to say
Knowing the lesson isn’t the same as knowing what to do with it Monday morning. A security lead, a CISO, and a customer-facing team each need something different from this incident.
- What telemetry distinguishes account-data access from account modification?Correlate application, identity and database events.
- Were all 11.77 million passwords stolen?No such claim is supported by Capcom's disclosure.Capcom reported approximately 11.77 million affected email and metadata records and 196 unauthorized password changes; it did not confirm theft of original customer passwords.
- What should customers watch for?Capcom warned of fraudulent messages impersonating the company or related parties.
References & confidence
- ConfirmedCapcom — Notice and Apology Regarding Customer Information Affected Through Unauthorized Access (22 October 2026). https://www.capcom.co.jp/ir/english/news/html/e261022.html — Primary company statement for impact, dates, exclusions and response.
- Analytical inferenceDKCISSP editorial security analysis — Recommended controls are not a claim about Capcom's undisclosed architecture.