Breach · 5 min read
Rakuten Securities says a test system may have leaked millions of customer profiles
The broker’s November 17 notice says login IDs for up to about 11.25 million accounts, and fuller financial profiles for up to about 4.47 million, may have left a test system.

Rakuten Securities, the Japanese online broker, said on November 17, 2026 that an outsider may have taken customer information it kept in a test environment. Its notice (PDF, in Japanese) is the company’s own account. ITmedia reported the same figures the same day.
Up to about 11.25 million accounts may have had a branch code, a customer code and a login ID exposed. ITmedia reads the notice as putting a fuller financial profile inside that set, for up to about 4.47 million accounts. Passwords and trading PINs are not on the list the company has confirmed.
What the notice says was taken
Rakuten Securities says that on Monday, November 16, it detected possible unauthorized access to part of its systems, cut that access off, and fixed the affected part. The investigation then found that some information held in a test-environment system may have leaked on Wednesday, November 11. The cause, and the path the outsider used, are still under investigation.
The notice lists two layers, and ITmedia reads the fuller profile as sitting inside the larger count. Both include people who have already closed their accounts.
Up to about 11.25 million accounts may have had the branch and customer code and the login ID exposed. The company says that login ID is not the Rakuten ID used across other Rakuten services.
Within that, up to about 4.47 million accounts may also have had the name in kanji and in kana, the date of birth, the address, the phone number, the email address, the employer, the bank account registered for withdrawals (the bank, the account number and the account holder), the annual income and financial assets the customer declared, holdings by product, and the date of the last login.
The notice says the company has not confirmed a leak of the password, the PIN, or other information needed to place a trade. As of the notice, it has also not found an unauthorized login or an unauthorized trade that it ties to this incident. It says it has finished identifying the customers who are affected and will contact each of them. If it learns something new that it should announce, it says it will write again.
The notice does not say why production customer details were in a test environment, or why five days passed between the possible leak on November 11 and the detection on November 16.
What the company is asking customers to do
Rakuten Securities says the email it sends does not contain a web address, and that it does not ask for personal information or login details by phone. It asks customers to treat an email, a text, a call or a letter that claims to be from the company or a group company as suspect, and not to open a link in it or type details into it.
It is making passkey login mandatory. It says more than 90 percent of customers who log in on a given day already use one, and it asks anyone who has not set a passkey up to do so. From the security settings page, after a person has logged in themselves, they can also pause trading and withdrawals for a time.
What you can do
- If you have a Rakuten Securities account, set up the passkey from the company’s own site or app, not from a link in a message. The company is making that login mandatory.
- If you want a pause while you read the notice, use the security settings page the company describes, after you have opened the site yourself. That pause is for trading and withdrawals. It is not a substitute for the passkey.
- Do not send a password, a PIN or a one-time code to anyone who writes or calls about this notice. The company says its own email has no link, and that it does not ask for those details by phone.
- A login ID is not the same as a password. The larger figure is that identifier, plus the branch and customer codes. Up to about 4.47 million of those accounts may also have had the fuller profile. Neither figure, on the company’s account, includes the password. The identifier is still enough for a targeted message.
- If you also use other Rakuten services, the notice says this login ID is not your Rakuten ID. Do not assume a password change on a shopping account fixes the brokerage login, or the other way around.
How Frame helps
If this breach is added to a catalog, add it to a verified email in Frame and Frame shows what it exposed, gives you a short checklist and counts it in your exposure report. Frame can also look up your verified emails in Have I Been Pwned’s breach database. Frame’s email aliases also let you give a broker its own address, so a message that arrives at the wrong one stands out. Frame never collects or stores the leaked records themselves, and it does not hold a brokerage login.
Related coverage
- SMBC Consumer Finance: data on up to 320,118 loan customers taken, including licence numbers and income: a different Japanese lender, and a different system, disclosed earlier in November.
- How scammers use leaked data to make phishing personal, and how to spot it: why a message that already knows your name and your broker can still be fake.
Sources
- Rakuten Securities, 楽天証券のお客様の情報漏えいの可能性に関するお詫びとお知らせ (PDF, in Japanese), November 17, 2026
- ITmedia NEWS, 楽天証券に不正アクセス、最大1125万口座のIDなど漏えいか (in Japanese), November 17, 2026
More stories
New posts, by email.
About once a month. Plain-language privacy notes, nothing else. I never share your address.


