It Leaked from the Place for Testing — Rakuten Securities Customer Data, Up to About 11.25 Million Accounts at Risk of a Leak

Hello, I am Kurashiki Bouzu (kurashiki-bouzu), born in 1971. I am a former funeral director, and I now live in an old house in Kurashiki, Okayama, working together with my AI butler, Moka.
This time, the story was announced only recently, on November 17. Information from securities accounts may have leaked, the announcement said. The place it leaked from was not the live system customers use, but “the place for testing.” Real information had been placed in the place for testing. That is the story.
The result first
The conclusion, up front:
- On November 17, 2026, Rakuten Securities announced that, due to unauthorized access by a third party, some customer information may have leaked (company press release)
- The information that may have leaked was managed inside a test-environment system. The leak happened on November 11, and it was detected on November 16 (same press release)
- Up to about 4.47 million accounts may include names, addresses, and even withdrawal bank accounts; up to about 11.25 million accounts involve only the branch and customer code and the login ID. The figures include people whose accounts have already been closed (same press release)
- No leak of passwords or PINs needed for login has been confirmed, and as of now, no unauthorized access or fraudulent transactions believed to have been caused by this incident have been confirmed either (same press release)
- Rakuten Securities is calling on customers to set up passkey authentication, and to set a temporary suspension of transactions and withdrawals. It also announced that emails from Rakuten Securities contain no URLs (same press release)
What happened — the place for testing held the live information
Here is the sequence, in date order.
On Wednesday, November 11, 2026, some of the information managed inside a test-environment system at Rakuten Securities may have leaked to the outside — this became clear in the investigation that followed. On Monday, November 16, the company detected a possible unauthorized access by a third party against some of its systems, and blocked access to the affected part and fixed it. Then, on November 17, it announced that a leak may have occurred.
A test environment is a place for trying out a new system, to see whether it works, before it is put into live use. Normally, real information is not placed in a place for testing. This time, however, customer information was being managed inside a test-environment system. According to the announcement, the cause of the unauthorized access and the detailed circumstances are still under investigation.
To put it in terms of a house: the safe in the main house was solid. But the safe in the annex built for practice also held real passbooks. If the annex lock is broken, the passbook information gets out. It was not the live system that was broken into; the information placed in “the place for testing” was what leaked.
What leaked, and what did not
The announcement divides the information that may have been taken outside into two groups.
1. Up to about 4.47 million accounts — the following information may have leaked together:
- Rakuten Securities branch and customer code, login ID
- Name, name in kana, date of birth, address, phone number, email address
- Employer
- Withdrawal bank account (financial institution, account number, account holder name)
- Annual income and financial assets (as reported by the customer)
- Asset information by product, date of last login
2. Up to about 11.25 million accounts — only the Rakuten Securities branch and customer code and the login ID are involved.
Some reports describe the two figures added together as “a maximum of about 15.72 million records.” The official announcement writes the two groups separately, and whether the two groups overlap cannot be read from the announcement. This article keeps the official split as it is.
What did not leak is also stated clearly in the announcement. No leak has been confirmed of the password needed for login, or of the various items of information, including PINs, needed for transactions. Nor, as of now, has any unauthorized access or fraudulent transaction believed to have been caused by this incident been confirmed.
The company has finished identifying the customers confirmed to be affected, and says it will contact those customers individually.
For people who hold a securities account — things to check right now
That no password leaked does not mean there is nothing to do. With a login ID together with a name, address, date of birth, phone number, and email address, a message pretending to be from a securities company can be made to look convincing. Following the official call in the announcement, here are the things to check:
- Set up a passkey: Rakuten Securities is working to make login by “passkey authentication,” which uses a fingerprint or face recognition, mandatory. According to the announcement, more than 90% of customers who log in every day already use passkey authentication. If you have not set it up yet, please do so. The passkey guide is on the official Rakuten Securities website
- Transactions and withdrawals can be stopped temporarily: You can set a temporary suspension of various transactions and withdrawals yourself. After logging in to the Rakuten Securities website, set it on the security settings page. For an account you will not use for a while, stopping it is one option
- Emails from Rakuten Securities contain no URLs: The announcement states this plainly. Please do not go to a login screen from a link inside an email. When you log in, the sure way is to enter through the official site you have bookmarked yourself, or an official address you typed in yourself
- They never ask for information by phone: The announcement also says that Rakuten Securities never asks for personal information or login-related information by phone. If a caller saying “This is Rakuten Securities” asks for your PIN or an authentication code, do not answer on the spot; contact the official desk yourself
- Do not open or answer suspicious contacts: Please be careful of suspicious emails, SMS messages, phone calls, and postal mail impersonating Rakuten Securities or its affiliates. Do not access URLs written in a contact you were not expecting, or enter or give out personal information, as the announcement also calls for
That a login ID alone has leaked does not mean someone can get straight into your account. But the leaked information can become material for looking like the person somewhere else. If you reuse the same password across services, this is a good occasion to make the password for your securities account a separate one.
To close
The heart of this story is not “even a large securities company can be targeted.” The entry point was a test environment — a place that looked separate from the live system. And the fact that live information had been placed there is what made the leak large.
Looked at the other way, the way to protect is nothing special either. Keep how information is placed separate between the place for testing and the place for live use. On the reader’s side: put in a passkey, stop what can be stopped, and check contacts through the official entry point. The November announcement reads, as it stands, as a checklist for people who hold a securities account.
Sources: Rakuten Securities Inc., “Apology and notice regarding the possibility of a leak of Rakuten Securities customer information” (November 17, 2026). The company’s passkey authentication guide (https://www.rakuten-sec.co.jp/web/security/passkey/guide/ ) and its guide to the temporary suspension of transactions and withdrawals (https://www.rakuten-sec.co.jp/web/security/account_lock/ ).
Entrance (other languages)