Key takeaways
- Rakuten Securities, one of Japan's largest online brokers, said on November 17 that customer data held in a system in its test environment may have been taken out on November 11. It noticed the unauthorized access on November 16.
- For up to about 4.47 million accounts, the data includes names, addresses, birth dates, phone numbers, email addresses, employers, bank accounts used for withdrawals, customers' own declarations of annual income and financial assets, holdings by product and last login dates. For up to about 11.25 million accounts, it includes customer codes and login IDs. Customers who have closed their accounts are included.
- No passwords or PINs were found to have leaked, and no unauthorized trading has been found. More than 90% of customers who log in each day already use passkeys.
- In our view, that contrast is the lesson. Japan's brokers have spent the past year and more hardening the login. Here the data was in a place that login does not protect: a copy, outside production. Real customer data in a test environment has to be handled with great care, and in most cases should not be there at all.
What happened#
According to Rakuten Securities' notice:
| Date | Event |
|---|---|
| Wed, Nov 11 | Information held in a system in the test environment may have leaked outside the company |
| Mon, Nov 16 | Rakuten Securities detects possible unauthorized access to part of its systems, blocks access and fixes the affected part |
| Tue, Nov 17 | Public notice; affected customers have been identified and will be contacted individually |
That is five days between the possible leak and its detection. Rakuten Securities has not said how the attackers reached the test environment, whether the data was actually taken, or why it was there. The cause is under investigation.
What may have been taken#
| Data | Accounts (maximum) |
|---|---|
| Branch and customer code, login ID (not the Rakuten ID), name, name in kana, birth date, address, phone number, email address, employer, withdrawal bank account (bank, account number, holder), self-reported annual income and financial assets, assets by product, last login date | about 4.47 million |
| Branch and customer code, login ID | about 11.25 million |
Both groups include customers who have closed their accounts. Rakuten Securities says passwords, PINs and other information needed to trade were not found to have leaked, and that it has found no unauthorized access or trading caused by this.
It is now on our list of 2026's largest breaches. It is Rakuten Securities' third notice in three weeks, but the first about its own systems: on October 31 it reported 362 bond buyers' records exposed through the digital bond perks platform of NTT Data's contractor, and on November 5, 2,109 email addresses of subscribers to a third-party alert email, sent through the breached Arara Message service.
The front door was locked#
Japanese brokers spent much of 2025 fighting a wave of account takeovers, in which attackers used stolen credentials to log in as customers and trade with their money. The industry's answer was stronger login: multi-factor authentication and passkeys, which phishing cannot steal. By September 2026, monthly unauthorized trades had fallen to almost none, as we noted in our Iwai Cosmo article. Rakuten Securities says more than 90% of customers who log in on any day now use passkeys, and it is making them mandatory.
None of that protects data that has been copied somewhere else. A test environment is not reached through the customer login. It is reached by developers, testers and often contractors, through networks and accounts set up for building and checking software, and it is usually watched less closely than production.
Why this data is dangerous#
The login IDs and the profiles together give an attacker almost everything needed for a convincing approach except the password:
- A message that quotes a customer's real login ID, employer, bank and holdings will be far more believable than generic phishing.
- Income and asset declarations show who is worth targeting.
- Bank details and employers make phone and postal scams easier as well as email ones.
Rakuten Securities says its emails never contain links, and that it never asks for personal or login information by phone. Customers can also suspend trading and withdrawals themselves in the security settings after logging in.
What we don't know yet#
- How the attackers reached the test environment, and whether the data was actually taken
- Why real customer data, including closed accounts, was in a test environment, and in this volume
- Who used the environment, staff or contractors, and how it was protected and monitored
- Whether the data was masked in any way
- How the Financial Services Agency will respond
Our view#
Real customer data in a test environment must be handled with great care. Testing a brokerage system with realistic data is understandable: edge cases in names, addresses and accounts are hard to invent. But the test environment held millions of customers' bank accounts, incomes and holdings, including people who had left. In our view, the default should be synthetic or masked data. Where real data is truly needed, it should be limited to the fields and the number of records the test requires, with account numbers, incomes and asset values masked, and deleted when the test ends. Closed accounts have no place there.
If real data is there, protect it like production. A copy of production data is production data, whatever the environment is called. The same access controls, the same monitoring and the same limits on what can reach it from outside should apply. Five days between the possible leak and its detection suggests the test environment was not watched as closely as the trading systems.
Locking the front door is not enough. Rakuten Securities has done the hard work on customer login. This case shows that a breach does not need the login. As with ApplyNow, whose analysis tool could read its live databases, the weak point was a second place where the data lived. Every copy of customer data, for testing, analysis, backups or vendors, is another front door, and each needs its own lock.
What this means for customers#
- Expect convincing phishing and calls that quote your login ID, employer, bank or holdings. Rakuten Securities' emails contain no links; log in through the app or a bookmark.
- Use passkeys, and consider the setting that suspends trading and withdrawals when you are not using the account.
- If you closed your account, your data may still be in scope; the same caution applies.
What this means for practitioners#
- Inventory every copy of customer data: test, staging, analysis, backups, exports and vendors.
- Use synthetic or masked data for testing by default, and require approval, minimization and an expiry date for any exception.
- Treat test environments holding real data as production for access, monitoring and network exposure.
- Never copy closed or dormant accounts into non-production environments.
Japanese terms at a glance#
| Japanese | Reading | Meaning |
|---|---|---|
| テスト環境 | tesuto kankyō | Test environment |
| 本番環境 | honban kankyō | Production environment |
| 出金先口座 | shukkin-saki kōza | Account used for withdrawals |
| 年収・金融資産 | nenshū / kin'yū shisan | Annual income and financial assets |
| ログインID | roguin ID | Login ID |
| パスキー認証 | pasukī ninshō | Passkey authentication |
| 退会 | taikai | Account closure |
| 利用停止 | riyō teishi | Suspension of use |