Cyber & AI intelligence
Briefs indexed3801
Issues37
Published Mondays07:30 CT
▣ Breach RAKUTEN-SECURITIES 2026-11-18

Rakuten Securities: Customer Data Leaked From a Test Environment

"Rakuten Securities, Japan's largest online broker, said on November 17 that an outside party may have taken customer information from a system in its test environment on November 11. The company's notice puts login IDs…"

Rakuten Securities, Japan's largest online broker, said on November 17 that an outside party may have taken customer information from a system in its test environment on November 11. The company's notice puts login IDs plus branch and customer codes at risk for up to about 11.25 million accounts. For up to about 4.47 million accounts, the exposed data also includes names, addresses, employers, withdrawal bank accounts, declared income and holdings. How many accounts are affected in total is disputed. Most coverage treats the 4.47 million as part of the 11.25 million, but a company spokesperson told IT journalist Kenta Yamaguchi that the two groups do not overlap, which would put the maximum at about 15.72 million accounts, former customers included (ASCII.jp). The company says passwords and trading PINs have not been confirmed leaked and it has found no unauthorized trades. No attacker has been named. The breach follows earlier incidents at Rakuten Travel and Rakuten Drive.

What Happened

All outlets give the same sequence of events, drawn from the company's notice:

That leaves a five-day gap between the leak and its discovery. The cause and the route the attacker used are still under investigation, the company says. As of November 17 it had found no unauthorized logins or trades linked to the incident.

This is the third Rakuten Group business to report unauthorized access in recent months. The Japan Times reports that Rakuten Drive disclosed exposure of data, including photos and documents, from more than 15,000 accounts through access between January 29 and September 17. It also reports that Rakuten Travel disclosed two separate incidents in September and October that exposed names, email addresses and phone numbers for more than 2.6 million accounts. No public statement has linked the three incidents to a common attacker or cause.

What Was Taken

The notice describes two groups of data, and both include customers who have already closed their accounts:

On the total, accounts differ. Frame, citing ITmedia, reads the 4.47 million as sitting inside the 11.25 million, and the Japan Times and Tokyo Dispatch describe it the same way. ASCII.jp reports, through Yamaguchi's Yahoo! News Expert piece, that a spokesperson said the groups do not overlap, for a combined maximum of about 15.72 million. That higher figure fits a separate report from the Tech By Country blog that the broker had more than 15 million customer accounts as of November 2. If the spokesperson is right, nearly every account the broker has ever held may have had at least its login ID exposed.

Passwords, PINs and other information needed to trade are not on the list of confirmed exposures.

Why It Matters

Together, these records amount to an almost complete profile of each investor: who they are, where they live and work, where their money goes when they withdraw it, how much they say they own, and the ID they log in with. Only the password and second factor stand between an attacker and the account.

The broker's login was not the weak point. The Japan Times and Japan Cyber Watch report that about 90% of daily users already sign in with FIDO2 passkeys. The Japan Times says passkeys will eventually become mandatory, with no timeline announced, while the Tech By Country blog describes the company as making passkey login mandatory. Japan Cyber Watch argues that this contrast is the main lesson. Japanese brokers have spent more than a year hardening the login, but here the data sat in a copy outside production that the login does not protect.

For the next few months, expect targeted phishing. Leaked contact details, combined with real asset figures and employer names, make convincing lures, whether by email, SMS, phone or post. The company has warned customers to watch for messages pretending to come from Rakuten Securities or its affiliates. The Japan Times also reports that the company advised users to temporarily suspend transactions and services. No other outlet repeats that advice.

The Attack Technique

How the attacker got in has not been disclosed, and the company says it is still investigating. The clearest explanation of why real data was exposed at all comes from the spokesperson's comments reported by ASCII.jp. The test environment normally used dummy data, but an internal system update required testing with production data. The unauthorized access happened while real customer records were present in the test environment.

That points to a familiar failure: a non-production system holding live data with weaker controls and less monitoring than production. Whether the attacker used stolen credentials, an exposed service or a vulnerability in the test system has not been reported. No group has claimed the attack, and none has been attributed.

What Organizations Should Do

  1. Keep production data out of test environments. Use synthetic or masked data by default. If live data is truly required, approve it for a fixed window, record who signed off, and delete it on a schedule.
  2. Protect non-production like production when it holds real data. That means the same access controls, network isolation, logging and alerting. Five days between the leak and its detection is too long.
  3. Keep an inventory of data copies. Track every location that holds customer records, including test, staging, analytics and backup systems. Include closed-account records and enforce retention limits on them.
  4. Assume a phishing wave will follow any profile leak. Warn customers early and specifically, and tell them which channels you will never use to ask for credentials.
  5. Finish phishing-resistant authentication. Passkeys at 90% adoption left a 10% gap, and leaked login IDs make that gap easier to target. Set a deadline for making them mandatory.
  6. Watch for account-takeover attempts. Monitor for credential stuffing and changes to registered withdrawal bank accounts, since attackers now know the existing ones.

Sources: Rakuten Securities account information compromised in major data br... | Rakuten Securities reports breach affecting up to 11.25 million acc... | Rakuten Securities data breach may have exposed 4.47M accounts | Rakuten Securities says a test system may have leaked millions of c... | Rakuten Securities breach: 11.25M accounts at risk · Osegi | Rakuten Securities: Bank Accounts and Income of 4.47 Million Broker... | Rakuten Securities: Up to 15.72 Million Accounts Potentially Leaked... | Rakuten Securities Data Breach Explained: 4.47 Million Accounts Exp...