The Rakuten Securities data breach exposed login IDs for up to about 11.25 million accounts, and personal and banking data for up to about 4.47 million of them. Rakuten Securities, Japan’s largest securities company by disclosed non-consolidated account numbers, said customer information held in a test-environment system may have leaked after unauthorized access on Wednesday 11 November, and announced the incident on Tuesday 17 November, according to The Japan Times. The company has not confirmed any password or PIN leakage, and no unauthorized transactions have been confirmed so far.
The scale makes this the largest disclosure in Japan’s autumn wave of brokerage incidents. The company had more than 15 million customer accounts as of 2 November, NHK WORLD-JAPAN reported, which means the login IDs of about three in four accounts may have been exposed. Rakuten Group shares fell more than 7 percent on Wednesday morning before recovering somewhat, The Japan Times reported, closing down 5.67 percent, Arab News reported. Rakuten Bank closed down 15.16 percent at ¥4,489 after falling 19 percent intraday, the Colorado Tech Ledger reported.
What leaked, and what did not
The exposure came in two tiers, and the company drew the line between them clearly. Login IDs and branch and customer codes for up to about 11.25 million accounts may have been exposed. The login ID is separate from the Rakuten ID used across Rakuten Group services, according to CyberSixth.
For up to about 4.47 million accounts, including accounts that have already been closed, the data that may have been exposed goes much further: branch and customer code, login ID, name in kanji and kana, date of birth, address, phone number, email address, employer, the bank account registered for withdrawals (financial institution, branch, account type, account number and account holder), declared annual income and financial assets, holdings by product and the date of the last login. That is the field list from the company notice, as reported by CyberSixth.
What did not leak matters as much as what did. No leak of passwords or PINs needed to execute trades has been confirmed, and no unauthorized transactions or unauthorized logins linked to the incident have been identified so far, according to The Japan Times, NHK WORLD-JAPAN, MLex and CyberSixth. The company has identified the affected customers and will contact each of them individually, CyberSixth reported.
The remaining roughly 6.78 million accounts in the 11.25 million had login IDs and branch and customer codes exposed but not the sensitive fields, by our calculation (11.25 million minus 4.47 million). One figure to ignore: an aggregator cited about 15.72 million accounts as the affected total. That number adds the 11.25 million and the 4.47 million together, but the company’s own structure is that the 4.47 million accounts are a subset of the 11.25 million, not additional accounts.
How the Rakuten Securities data breach happened
The unauthorized access took place on 11 November, and the information that may have leaked was held in a test-environment system, according to the company announcement as reported by The Japan Times and CyberSixth. The company detected the possible unauthorized access on Monday 16 November, cut off access to the affected part of its systems and applied a fix. It published its announcement, titled “Apology and Notice Regarding Possible Leakage of Customer Information,” on Tuesday 17 November.
Five days passed between the possible leak on 11 November and detection on 16 November. The company has not explained how the attacker reached the test environment or why detection took that long.
The cause and the detailed sequence of events are still under investigation, according to CyberSixth and NHK WORLD-JAPAN. No attacker group has been named in any source, and no ransom demand or data-publication claim has been reported.
The FIDO2 reassurance misses the point
Rakuten Securities has been introducing FIDO2-based authentication. As of Tuesday 17 November, 90 percent of daily users had already set a FIDO2 passkey, and the login method will eventually become mandatory, The Japan Times reported.
That is a genuine improvement to login security, and it matters for the exposed accounts: a login ID on its own is not enough to enter an account once a passkey is in place, as CyberSixth notes, and The Japan Times says passkeys are expected to reduce the risk of unauthorized access and phishing. But it does not address how this incident happened. The leaked data was held in a test-environment system, and the company has not said how the attacker reached it, so the enrollment figure says nothing about why real customer data was sitting in a test system. That distinction is TechReview’s analysis, not the company’s framing.
The company advised users to temporarily suspend transactions and services, and to watch out for suspicious emails, SMS messages, phone calls and mail impersonating the company or its affiliates, according to The Japan Times and NHK WORLD-JAPAN. That advice is worth following, but it should be verified through the official app, not through a link in a message. The company says its emails contain no links and it never asks for personal or login details by phone, according to CyberSixth.
Japan’s autumn brokerage breach wave
Rakuten Securities is not an isolated case. Its disclosure is the largest of the figures reported in a wave of unauthorized-access incidents at Japanese financial firms this autumn, and the comparison below is TechReview’s own.
| Company | Disclosure | Sensitive-data accounts | Entry point |
|---|---|---|---|
| Rakuten Securities | 17 Nov 2026 | 4.47 million (11.25 million login IDs) | Test-environment system |
| SMBC Nikko Securities | Week of 10 Nov 2026 | 56,000+ | Not stated |
| Rakuten Travel | Sep and Oct 2026 | 2.6 million+ (names, emails, phones) | Not stated |
| Rakuten Drive | Oct 2026 (access Jan to Sep) | 15,000+ | Not stated |
| Daiwa, IwaiCosmo, Sony Bank | 2026 | Counts not stated | External service providers |
SMBC Nikko’s disclosure, reported last week, covered names, addresses, account numbers and bank balances for more than 56,000 accounts. Rakuten Securities’ 4.47 million sensitive-data accounts are about 80 times that figure, by our calculation (4,470,000 divided by 56,000 is 79.8). Against a roughly 15 million account base, about 75 percent of all Rakuten Securities accounts had login IDs exposed (11.25 million out of 15 million), and about 30 percent had sensitive personal and banking data exposed (4.47 million out of 15 million). The company says the base is more than 15 million, so these are upper estimates and the actual percentages are slightly lower. Both percentages are TechReview’s estimates from the company figures.
Two other Rakuten Group businesses disclosed cyberattacks last month, according to the same Japan Times report. Rakuten Drive reported data from more than 15,000 accounts exposed through unauthorized access between 29 January and 17 September 2026, a span of nearly eight months by our count, and disclosed it in October. Rakuten Travel reported two separate unauthorized-access incidents in September and October, with names, email addresses and phone numbers attached to more than 2.6 million accounts exposed. Daiwa Securities, IwaiCosmo Securities and Sony Bank faced leaks related to external service providers rather than their own systems. The Japanese government announced a package of emergency measures earlier in November 2026 to address the series of unauthorized-access incidents.
What to do if you hold a Rakuten Securities account
If you hold an account, assume your login ID may be among the exposed ones and act on the sensitive-data risk first. The combination of declared annual income, financial assets, holdings by product, employer and withdrawal bank account details gives a phisher enough material to write a message that reads like it came from the brokerage itself, so verify every message through the official app and set up the FIDO2 passkey if you have not already.
- Wait for the company’s individual contact, and check the official app or website for your account status rather than clicking a link in an email or text.
- Watch for phishing that uses your leaked details, including messages that quote your income, employer or bank account to sound legitimate.
- Set up the FIDO2 passkey on your account, since the login method will eventually become mandatory.
- Verify any message telling you to suspend transactions through the official app, not through a link in the message itself.
- Report suspicious emails, texts, calls or mail impersonating Rakuten Securities to the company through its official channels.
- As a general precaution, change any password you reused on Rakuten Securities elsewhere, since a leaked login ID becomes far more useful to an attacker paired with a reused password.
What to watch next
Whether the incident has been reported to Japan’s Personal Information Protection Commission or the Financial Services Agency. The company has not said, according to CyberSixth. Whether the cause and the detailed sequence of events are disclosed, since both are still under investigation. Whether any leaked data is misused beyond the company’s statement that no unauthorized transactions have been identified so far. Whether the company confirms it has contacted the affected customers, since it has said it will contact each of them individually. And whether the FIDO2 mandate gets a timeline.
The Rakuten Securities data breach is a test-environment failure: the leaked data was held in a system full of real customer data, and the fix has to reach the test systems, not just the login screen. The FIDO2 figure matters for protecting the exposed accounts, but it does not explain why their data was in a test system in the first place.


