Capcom says 11,774,247 account records were exposed. Its October 23 update says 19 of those reached a store page.
Capcom says 11,774,247 CAPCOM ID records were exposed. An October 23 update says 19 Japanese store profiles were opened. Both notices say card numbers were not included.
The short version
Capcom's October 22 notice says 11,774,247 CAPCOM ID records were exposed, mostly email and account metadata. Forty-three also had demographic fields, and 196 passwords were changed and then reset. The October 23 update says 19 of those 196, in Japan, had a store profile opened. Both notices say card data was not included. Nikkei reported the first totals.
Two notices, two counts
Capcom Co., Ltd. posted an English notice on October 22, 2026 and an English update on October 23. The first says a third party gained unauthorized access to CAPCOM ID, the account used for Capcom's web services and for playing certain games online. The count is 11,774,247 records worldwide for email addresses and what Capcom calls system-specific identifier information: account creation time, last login time, login count, and the client address used at last login. Inside that total, 43 records also included date of birth, gender, country or region, and nickname. Separately, 196 accounts had login passwords changed without authorization. Nikkei's October 22 story reports the same totals. The October 23 update does not revise the 11,774,247. It adds a narrower finding about 19 store profiles.a session is not this account database.
What the 19 add
Capcom says it confirmed that a third party opened the e-Capcom account pages of 19 of the 196. e-Capcom is the company's online store in Japan. The update lists name, name in phonetic characters, telephone number, postal code, address, gender, date of birth, purchase history, inquiry history, and saved address-book information. It says those 19 records are in Japan, that the affected customers will be notified, and that it did not find this further exposure on the other accounts whose passwords had been changed. Nineteen is not a sample. It is the number Capcom says it finished counting. It does not shrink the email-record total. An email address from the first notice and a home address from the second are different fields, and only the second is limited to 19 people.New Mexico's order is a different defendant.
What Capcom says was not in the data
Both notices say credit card information was not included. The first notice says Capcom has not confirmed compromise of the passwords customers originally set, even though 196 passwords were changed and then reset by the company. A reset is a response. It does not reveal whether a mailbox was read before the reset. Capcom also says it will notify affected customers and that people should be wary of messages that pretend to be Capcom. That warning is about misuse of an exposed email address. It is not a description of how the access happened. This page does not describe how the access happened, because the notices do not, and because a method is not required to state the counts.the key stays with the holder.
The week, as the company orders it
October 19 is the detection day. Capcom says it blocked the access, confirmed unauthorized access had occurred, and started emergency measures the same day. October 20 is the internal headquarters and the confirmation that CAPCOM ID information was involved, plus a report to the company's external advisory body. October 21 is the report to the Osaka prefectural police and to the Personal Information Protection Commission. October 22 is the public notice. October 23 is the store-profile update. Nikkei, publishing on October 22, has the first notice's numbers and the timeline through the police report. It does not have the 19, because the 19 were not posted yet. A story written on October 22 is not wrong. It is earlier.Huntress's 79 is a different count.
Services stayed up, on Capcom's account
Capcom says the emergency measures are complete, that services using CAPCOM ID remain available, and that players can still access and play the games. A company can keep a login page up and still have lost a copy of the account table. The notice is the loss. The availability sentence is there so customers do not read the notice as an outage. This page will not read it as an all-clear. The investigation language in the first notice, that Capcom continues to assess the full scope, is why an update was possible a day later and why another update remains possible.what a TLS name binds.
Nikkei's job in this row
Nikkei is the outside account of the October 22 notice. It reports about 11.77 million records, the 43, the 196, the absence of card data, the reset, and the reports to police and the commission. It is a newspaper's rendering of a company release, in Japanese. Where a rounded 11.77 million and the exact 11,774,247 could be confused, this page uses Capcom's exact figure and treats Nikkei's rounding as the same total. Nikkei is not a source for the October 23 update.eMudhra left a different business.
Who is in scope
Holders of a CAPCOM ID, worldwide, for the email and metadata count. The 43, for the extra demographic fields. The 196, for a password that was changed and reset. The 19 in Japan, for the store profile. Players who never made a CAPCOM ID are outside the totals. Cardholders are in scope only through Capcom's statement that card data was not included. The company, as the party that posted the notices and that says it reported the incident to police and the commission.the Council mandate is not this incident.
What stays on the record
October 22, 2026 notice. 11,774,247 records, email and account metadata, worldwide. 43 with birth date, gender, country or region, and nickname. 196 passwords changed without authorization, reset, customer-set passwords not confirmed stolen. Cards not included. Services still up. Games still playable, on Capcom's account. Timeline October 19 through October 21 as detection, internal response, police and commission. October 23 update. 19 e-Capcom profiles in Japan, with name, contact, address, and purchase history. Other password-change accounts not found to have that further exposure. Nikkei, October 22, on the first totals. No method described here.
What would move the row
A third Capcom notice that changes either count, or a commission finding, would replace this row. A notice that card data was included after all would reverse the denial. Until then the record is the two English notices and Nikkei's account of the first.the advisory is the story.
Sources
The reports this brief is filing. Futureweb did not republish them.
Questions
Were passwords stolen?
Capcom says it has not confirmed that the passwords customers themselves set were taken. It says passwords were changed without authorization on 196 accounts, and that those passwords have been reset. A changed password and a stolen password file are different findings. Capcom is reporting the first and denying, so far, the second.
What are the 19?
The October 23 update says that of the 196 accounts with a changed password, 19 had their pages on e-Capcom, Capcom's Japanese online store, accessed by a third party. The fields Capcom lists are name, phonetic name, telephone, postal code, address, gender, birth date, purchase history, inquiry history, and address book. It says other accounts showed no further compromise from the password changes. The 19 are Japan-only, in the update.
Were credit cards included?
Both notices say credit card information was not among the affected information. A denial in a company notice is the company's finding as of that date. It is not a bank's letter. This page treats it as Capcom's statement, repeated on two days.
Can people still play?
Capcom says emergency measures are done, CAPCOM ID services remain available, and the incident does not stop players from accessing or playing its games. Availability of the service is not a claim that the records were unexposed. The records are the point of the notice.
What is the timeline Capcom gives?
October 19: suspicious activity detected, access blocked, unauthorized access confirmed, emergency measures. October 20: an internal response headquarters, confirmation that CAPCOM ID information was accessed, report to an external advisory committee. October 21: report to Osaka prefectural police and to Japan's Personal Information Protection Commission. October 22: the first public notice. October 23: the update about the 19 store profiles.