packet-autopsy.com

Case 007 · Incident: 19 Oct 2026

Capcom: Hackers stole 11.7M emails from the Resident Evil maker

Capcom says attackers got unauthorized access to CAPCOM ID, its shared account system for web services and online games. The attackers exposed 11,774,247 email addresses along with account metadata: creation date, last login date, number of logins and the IP address of the last login. For 43 accounts, date of birth, gender, country/region and nickname were also exposed, and the attackers changed the passwords on 196 accounts, which Capcom then reset.

Watch on YouTube

The Notice

Capcom says attackers stole the email addresses of 11,774,247 people from its shared account system. On 196 of those accounts, they went further, changing the passwords to lock the real owners out.[1][2] Capcom's team detected suspicious activity on October 19, 2026, and confirmed unauthorized access the same day. They began blocking it while they investigated what had happened.[2][3] Three days later, on October 22, the company disclosed the breach in a notice on its investor relations site.[4]

Capcom has said almost nothing about who did this or how. But its statements, as reported by several outlets, let us piece together its response day by day. This episode follows that response from the defender's side: what Capcom says it saw, what it did, and what it still has not said.[2][4]

The Target

Capcom is a Japanese video game developer and publisher. It is the company behind Resident Evil, Monster Hunter, Street Fighter and Mega Man. BleepingComputer reports that it has 4,000 employees.[2] CAPCOM ID is the company's shared account system. One login gives access to its web services and to some of its online games.[2] Shared accounts are convenient for players. They also gather millions of records in one place. Kotaku describes this incident as a direct breach of the databases and services that held that user information.[2][5]

Alongside each email address, the attackers took account metadata. That is the date the account was created, the date of the last login, how many times the owner had logged in, and the internet protocol address of that last login, meaning the network address the player connected from.[1][2]

Four Days in October

The clock starts on October 19. Capcom says it detected suspicious activity that day, confirmed unauthorized access, and began blocking the activity while the investigation ran.[2][3][4] That order matters. Containing first and investigating in parallel limits how much more an intruder can do while analysts work out the scope.[3] The investigation started immediately. By the next day, October 20, it was clear that customer data had been taken, and Capcom set up an internal incident response headquarters.[2][4]

Capcom says the internal incident response headquarters was set up on October 20. It has not described how that group worked. As general context, and not something Capcom has said, companies often use a group like this to coordinate containment, official reporting and communication in one place.[4] On October 21, Capcom reported the incident to the Osaka Prefectural Police and to Japan's Personal Information Protection Commission. Official reporting came first, before any public statement.[1][4] Detection to public notice took three days. That is fast, but speed only covers what Capcom could see. When the intrusion actually began is still unknown.[2][4]

Here the sources diverge. Kotaku reported that the breach occurred on October 19, with the vulnerability fixed internally right away.[5] But BleepingComputer says the timing of the breach remains unclear, and Capcom has not said when the intrusion began. October 19 is the day of detection. It may not be the day the attackers arrived.[2][4]

Signals and Triggers

So what did the defenders actually see? In Capcom's account, it detected suspicious activity and confirmed unauthorized access on October 19. That brief description is what the sources give us about the moment of detection.[2][3] Consider the signals that could have existed. However the attackers did it, more than 11.7 million records ended up in their hands. Unusually large reads from an account database are exactly what database monitoring is built to flag. Whether such an alert fired here, Capcom has not said.[1][2] A second possible signal was the password changes on 196 accounts. A burst of changes, followed by owners unable to sign in, can surface in authentication logs and in support requests. Whether those changes tipped Capcom off is not public.[1][2]

There was outside context too. On October 19, Square Enix confirmed that an unnamed third party had accessed a number of Final Fantasy XIV accounts. Kotaku attributes that to credentials reused from other breaches.[5] Nothing in the sources connects the two incidents. But for any games company that week, a peer's account problem was a reason to look harder at its own login traffic.[5] Kotaku also places the Capcom incident within a recent surge of AI-powered attacks on Japanese companies. It does not say AI was used against Capcom, and nothing in the sources establishes that.[5]

According to Kotaku, the Japanese government is looking at ways to respond, with breach cases in 2026 already surpassing the total for all of last year.[5] So here is the contrast. Several kinds of signal could have existed before October 19. The public record shows only the moment Capcom recognized suspicious activity, and everything it did after that.[1][2]

What Was Taken

Most of the exposure is wide but shallow. For a small subset of 43 accounts, it went deeper: dates of birth, gender, nicknames and country or region were also exposed.[2] For 196 accounts, the attackers changed the login passwords in an attempt to lock the owners out. Capcom stepped in and reset them.[2] Capcom says passwords for all other registered members were not exposed, and credit card information was not affected. It found no evidence that the passwords customers originally set were leaked.[2][3]

That leaves a puzzle. Hardware Busters points out that changing a password normally means knowing the current one, or reaching the account another way. That could be a live session, meaning an already signed-in connection, a recovery flow like a forgotten-password process, or an administrative function used by staff.[3][4] Capcom has not said which applied here. It is also unknown whether the 196 changes were part of the same intrusion or a separate attempt to take over accounts.[2][4] Through all of this, the services stayed up. Capcom says all services that use CAPCOM ID remain available.[1]

The bigger risk now is what comes next. Hardware Busters says the likeliest follow-on is targeted phishing, meaning fake messages crafted to trick a specific person, because the stolen data is so heavily weighted toward email addresses and login history.[4] Notebookcheck says the data could be used for phishing that pretends to come from Capcom or related companies. A message that mentions when you created your account or last logged in looks far more convincing than a generic scam.[1][3]

Response and Unknowns

Capcom is notifying affected customers in stages, likely because of how many accounts are involved. In its own words, it has started to contact them sequentially and set up a dedicated contact point.[1][2] There is a toll-free line in Japan, and online inquiry forms for the Americas and for Europe, the Middle East and Africa.[4] Capcom also warned users to stay alert for unsolicited emails that impersonate the company or related entities, ask for more information, or carry links and attachments.[1][2]

On the cause, Capcom says it identified the intrusion method, shut it down and added security measures. It has not described that method.[1][2][4] No group has claimed responsibility. And nothing published so far connects this breach to the last time Capcom was hit.[4] That was in November 2020, when the Ragnar Locker ransomware gang claimed an attack on Capcom. Ransomware is malicious software used to lock up systems and extort the victim. The gang claimed it had stolen 1 terabyte of data.[2]

In April 2021, Capcom disclosed that those attackers got in through an old virtual private network device, the kind of gateway used for remote access to a company network.[2] Estimates of who was affected shifted. November 2020 coverage cited up to 350,000 people in Japan and North America. Capcom later warned that up to 390,000 could be affected.[2][6] The investigation is still under way and notifications are still going out, so the full picture may change. Capcom says it will prevent a recurrence based on the causes it identified, and further strengthen its information security.[1][2][3]

The Checklist

What can others take from this? Here is a checklist, first for the people who run account systems, then for the people who use them. Capcom saw something on October 19 and moved to block it. The harder question is what could have been seen earlier, and for any team running an account system, that is the question to answer first.[2][3]

What to do

  • One. Alert on bulk reads. Learn how many account records your applications normally query, and page someone when a service or user pulls far more.
  • Two. Treat password changes as security events. A spike in changes, or changes without a sign-in from a known device, should open an investigation, not just a support ticket.
  • Three. Lock down recovery flows and staff tools. Require strong authentication for administrators, and log and review every account change they make.
  • Four. Keep an inventory of internet-facing devices, and retire old remote access gateways that no longer receive updates.
  • Five. Write the response plan before you need it: who leads, who calls the police and the regulator, who drafts the customer notice. Rehearse it.
  • Six. Store less. Keep login history and personal details only as long as you truly need them, so any breach exposes less.
  • For players: change your password, and change it anywhere else you reused it. A password manager makes a unique password for every site easy.
  • Turn on two-step verification wherever your gaming accounts support it. That adds a second check, such as a code from an app, on top of your password.
  • And treat any email about a breach with suspicion. Do not click its links or open its attachments. Go to the company's site by typing the address yourself.

Open questions

  • When did the intrusion begin? Capcom has not said, and BleepingComputer calls the timing unclear. Kotaku says the breach 'occurred on October 19th', which may be confusing the breach date with the detection date.
  • How did the attackers get in? Capcom says it identified and closed the intrusion method but has not disclosed it.
  • How were the attackers able to change the passwords on 196 accounts when Capcom says it found no evidence passwords were compromised? Were those changes part of the same intrusion or a separate account-takeover effort?
  • Who is responsible? No group has claimed the attack, and nothing published links it to the 2020 Ragnar Locker incident.
  • Was the breach connected to the wider wave of AI-powered attacks on Japanese companies that Kotaku describes? The sources do not establish this.
  • What is the full scope and impact? Capcom's investigation is ongoing and customer notifications are still going out in stages.
  • Sources give different figures for the 2020 incident (up to 350,000 in Nov 2020 coverage vs up to 390,000 later). The 390,000 figure appears to be Capcom's later estimate.

Sources

  1. [1]SecurityWeek — 11 Million Impacted by Capcom Data Breach
  2. [2]BleepingComputer — Capcom confirms data breach affecting 11.7 million accounts
  3. [3]Notebookcheck
  4. [4]Hardware Busters
  5. [5]Kotaku
  6. [6]Tom's Guide