TBNGaming
Capcom Data Breach Results In Unauthorised Access To More Than 11.7 Million 'CAPCOM ID' Accounts
Publication: Nintendo Life | Latest Updates
Author: Not available in collected metadata
Source published: 23/10/2026, 03:55:00 UTC
Briefing created: 23/10/2026, 05:03:13 UTC
Based on a feed excerpt; full article content has not been acquired. Source evidence retrieved 23/10/2026, 04:37:25 UTC.
Briefings
A major data breach involving Capcom resulted in unauthorized access to over 11.7 million 'CAPCOM ID' accounts globally. The incident exposed sensitive personal information including emails, client IP addresses, and account creation dates. While 43 cases contained additional details like birth dates, gender, country/region, and nicknames, the majority of the leaked data remained limited to basic account identifiers. This breach occurred recently, with the article published on October 23, 2026, and the source is nintendolife.com.
Key points
- Capcom suffered a data breach exposing 11.7 million 'CAPCOM ID' accounts globally, including emails, client IP addresses, and account creation dates.
- Only 43 of the leaked cases contained additional sensitive details such as birth dates, gender, country/region, and nicknames.
Context
This incident represents a significant security vulnerability for a major third-party video game giant, potentially affecting millions of users worldwide. The specific nature of the breach and the scope of the data leak remain critical for understanding the impact on user privacy and security protocols.
Limitations
The evidence provided is limited to a single article snippet from nintendolife.com. It does not include the full scope of the breach, the timeline of the attack, the specific methods used to access the data, or the current status of the affected accounts. The article does not contain any additional background information or context beyond the headline and the initial summary of the breach.
Generated by Bittrees-hosted qwen35-2b sha256:aaf42c8b7c3c on 23/10/2026, 05:03:13 UTC. Based on publisher-provided feed evidence; may not cover the full original article. Check the source for details.
View archived briefing on IPFS
bafybeicvdqehygoffatios4u73icyeutm2yfe4lvymxpi4xfspmauib2ee