Capcom ID breach exposes 11.7M account email addresses
Teaser from the source
Capcom says a third party gained unauthorized access to CAPCOM ID, the account needed to play some Capcom games online. 11,774,247 records worldwide had email addresses plus account creation time, last login time, login count and last-login IP exposed; 43 also had date of birth, gender, country/region and nickname. Passwords were changed without authorization on 196 accounts (already reset). Capcom says it has not confirmed any leak of customer-set passwords, and no credit card data was involved. Detected Oct 19; reported to Osaka Prefectural Police and Japan's PPC on Oct 21. Expect phishing impersonating Capcom.
This is the RSS-feed teaser. Read the full article at the original source.
Read at pwn.watchMore on addresses
Other advisories
- Not ratedosv:CVE-2026-99092riscv: patch: fix handling of bpf-jit execmem addresses
- CriticalCVE-2026-106072A flaw in Node.js TLS hostname verification allows a certificate with only a DNS SAN to authenticate an IP endpoint when the client connects using a non-canonical IPv4 spelling, such as `0177.0.0.1`, `0x7f.0.0.1`, `2130706433` or `127.1`. `tls.checkServerIdentity()` did not classify these hosts as IP addresses, but normalized them to their canonical form and matched the result against the certificate DNS names. A certificate containing `DNS:127.0.0.1` and no `IP Address:127.0.0.1` SAN was therefore accepted, while the same certificate is correctly rejected for `127.0.0.1`. Exploitation requires a certificate with a numeric DNS SAN issued by a CA trusted by the client, and a platform resolver that accepts these spellings, such as glibc. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.
- CriticalCVE-2026-105483A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4 address when the host is written with non-ASCII characters, such as fullwidth digits (`127.0.0.1`). `tls.checkServerIdentity()` did not recognize such hosts as IP addresses, even though they normalize and resolve to a regular IPv4 address, and matched them against the certificate DNS names and Common Name instead. A certificate containing `DNS:127.0.0.1` or `DNS:*.0.0.1` could therefore be accepted for an IP endpoint it was not issued for. This is a regression introduced after the fix for CVE-2026-48618. This vulnerability affects Node.js **26.x** and **24.x**.
- Not ratedosv:CLEANSTART-2026-PU19584ip-address is a library for parsing and manipulating IPv4 and IPv6 addresses in JavaScript
- Not ratedosv:CLEANSTART-2026-AO39613ip-address is a library for parsing and manipulating IPv4 and IPv6 addresses in JavaScript
- Not ratedosv:CLEANSTART-2026-XD91859ip-address is a library for parsing and manipulating IPv4 and IPv6 addresses in JavaScript
- Not ratedosv:CLEANSTART-2026-WB16925ip-address is a library for parsing and manipulating IPv4 and IPv6 addresses in JavaScript
- Not ratedosv:CLEANSTART-2026-WK56892ip-address is a library for parsing and manipulating IPv4 and IPv6 addresses in JavaScript
Other news entries
- PHP2Shell Exploitation Moves From Probes to Working ShellsNewsSecurityWeek
- 11 Million Impacted by Capcom Data BreachNewsSecurityWeek
- Capcom confirms data breach affecting 11.7 million accountsNewsBleepingComputer
- CoinDCX loses 15.99M USDT from a retired TRON wallet compromised in its 2025 hackBreachpwn.watch
- Hackers Steal 1.8 Million Records From NikkeiNewsSecurityWeek
- University of Copenhagen breach exposes data of 525,000 peopleBreachpwn.watch
- Pizza Hut Japan: attackers accessed the online-ordering payment API, up to about 4.48M records exposedBreachpwn.watch
- Good Smile Company: official online shop breached, member details and partial card data possibly viewedBreachpwn.watch
Source: https://pwn.watch/i/capcom-id-breach-oct-2026