account takeover
6 articles with this tag
NIKKE (Goddess of Victory) PC Launcher Files Were Tampered With and a Malicious Program Was Distributed: What Windows Users Since September 27, 15:41 JST Should Do
On November 5, 2026, the operator of Goddess of Victory: NIKKE (Level Infinite) announced that some files of its PC launcher had been tampered with by a third party, so a malicious program could run when the launcher started. According to the operator, an external domain used by part of the game service was taken over on September 27, four official CDN scripts that the launcher downloads were tampered with at 15:41 JST that day, and distribution of the malicious program through those scripts began at 3:52 on October 30. It noticed the anomaly on November 4 and replaced the scripts to block further distribution. Anyone who started the Windows PC launcher at least once since 15:41 on September 27 is in scope; people who play only on mobile are not affected. The operator says the PC, accounts on external services and assets may be affected, and since 8:00 on November 5 it has offered a scan-and-remove function in the official PC client. The scope of damage and the route of tampering are under investigation. This site's take: if you are in scope, use a separate clean device to change passwords (email, banking, crypto, game stores, Discord first), sign out other sessions, re-issue API keys and tokens, and turn on two-factor authentication.
Capcom CAPCOM ID Breach (11,774,247 Records): Email Addresses and Login Data Leaked — What Account Holders Should Do
On October 22, 2026, Capcom Co., Ltd. announced that its online membership service CAPCOM ID (the shared account used for Capcom web services and some online games) was accessed without authorization by a third party, and that part of its customer information leaked. The leaked data are email addresses and system-specific identifier information (account creation date and time, last login date and time, number of logins, and the client IP address used at the last login), in 11,774,247 records worldwide. For 43 of them, date of birth, gender, country/region and nickname also leaked. On 196 of the accounts, the login password had been changed without authorization; the company has already reset those passwords. According to its second notice of October 23, for 19 of those 196 accounts (in Japan), an unauthorized third party accessed the account pages of e-Capcom, the company's online store in Japan, and the following leaked: name, name in Japanese phonetic characters, phone number, postal code, address, gender, date of birth, purchase history, e-Capcom inquiry history and saved address book information. For the remaining 177 of the 196 accounts, the company found no information compromised as a result of the password changes. The company says it has not confirmed any leak of passwords set by customers themselves, and credit card information was not among the affected data. According to the company, it found traces suggesting unauthorized access on October 19, immediately began blocking the access and investigating the cause and scope, and confirmed the unauthorized access the same day; on October 20 it confirmed the leak and the password changes; and on October 21 it reported the incident to the police and Japan's Personal Information Protection Commission. It says it has identified and addressed the attack method, but has not disclosed details of the cause. In the second notice it said the investigation into the scope of impact has been completed and that it will keep monitoring CAPCOM ID and related services. Services using CAPCOM ID and all games remain available. It said it would contact affected customers individually and set up dedicated support channels for each region. This site's take: CAPCOM ID holders should not open links in emails or texts claiming to be Capcom, should not give personal details over the phone, should change any password they reuse elsewhere, and should turn on two-factor authentication.
How to check if someone accessed your account: sign-in activity, signed-in devices and forwarding settings (Google, Microsoft, Apple, LINE, Instagram, X)
A guide to checking for unauthorized access. Look in three places: (1) sign-in activity and signed-in devices (Google 'Your devices', Microsoft 'Recent activity', Apple Account device list, LINE 'Devices', Instagram and Facebook 'Where you're logged in', X 'Apps and sessions'); (2) account settings (mail forwarding and filters, connected apps, recovery email and phone); (3) the device itself (iPhone configuration profiles, Android device admin apps, browser extensions). This site's take: changing the password alone can leave signed-in sessions, forwarding rules and connected apps in place. If you find something, sign out other sessions, change the password right away, then check recovery details, two-step verification, forwarding, connected apps and payments in that order.
Spam from your own email address: usually a forged sender, and how to tell if you were hacked
Most spam that arrives 'from' your own address is a forged sender field; your account was never touched. Japan's IPA and JC3 have both warned about extortion emails made to look like this, and IPA says its help desk has not seen a single case of footage actually being released. This site's view: the sender can write anything in the From field. Before you panic, spend five minutes on three places — Sent, sign-in history, forwarding rules. And if the email quotes a password you still use, change it today.
Password reset design flaws: 5 ways accounts get taken over despite strong login, and how to fix them
A reset flow is a mechanism for letting someone who does not know the password set a new one — which makes it an authentication path in its own right. Harden the login all you like: if reset is weak, reset is your real authentication strength. Five failure shapes: guessable tokens, tokens that never expire, links that live on in a mailbox, links whose destination can be set from outside (Host header), and responses that reveal whether an account exists. The key implementation step is separating what the guidance requires from the numbers it leaves to you.
7pay fraud (2019): the disclosed cause assessment and account protections
7pay suffered unauthorized account access in July 2019. The August 1 company statement assessed credential stuffing as likely and recorded 808 affected people and ¥38,615,473 as of July 31 at 17:00, including unauthorized top-ups and use. It had not found cases where reset functions were a direct cause. Separate that assessment from general advice on authentication, recovery and alerts.