Rakuten Securities Data Breach Explained: 4.47 Million Accounts Exposed in Japan — What Customers Must Do

rakuten securities data breach explained - Rakuten Securities logo

Image: Rakuten Securities logo (Wikimedia Commons, public domain).

TL;DR: Rakuten Securities data breach explained in one sentence: Japan's largest online broker says customer data from a test system may have leaked on 11 November, exposing detailed personal and financial records for up to 4.47 million accounts and login IDs for up to 11.25 million. Passwords were not confirmed leaked, and no unauthorised trades have been found — but the phishing risk that follows a breach like this is real.

Key Highlights

  • Rakuten Securities announced on 17 November 2026 that customer information held in a test environment may have leaked externally on 11 November, after it detected possible unauthorised access on 16 November.
  • Up to about 4.47 million accounts — including former customers — may have had names, addresses, phone numbers, employers, payout bank details, declared income and assets, and holdings exposed.
  • Up to about 11.25 million accounts may have had branch and customer codes and login IDs exposed; the two figures describe different data items.
  • No leak of login passwords or trading PINs has been confirmed, and no unauthorised logins or trades linked to the incident have been identified so far.
  • The cause and entry point are still under investigation, and the company is contacting affected customers individually and making passkey login mandatory.

Rakuten securities data breach explained: what happened

Rakuten Securities is Japan's largest online brokerage, with more than 15 million customer accounts as of 2 November. On Tuesday 17 November, the company published an apology and notice saying customer information may have leaked following unauthorised access to its systems.

The timeline is short and uncomfortable. Information held in a test environment system may have leaked on 11 November; the company detected possible unauthorised access on Monday 16 November, cut off access and fixed the affected part, and announced the incident the next day. That is five days between the possible leak and its detection — and the company has not said how the attacker got in, or why real customer records were sitting in a test system at all. A test environment is used for testing, not live trading, yet it held production data.

What data was exposed

The notice describes two groups of data. They cover different items, so the figures should not simply be added together — some reports that total them at 15.72 million are double-counting.

Data setAccounts affectedWhat it includes
Login IDs and account codesUp to about 11.25 millionBranch code, customer code and login ID
Full personal and financial profileUp to about 4.47 million, including former customersEverything above, plus name, date of birth, address, phone number, email address, employer, payout bank account details, declared annual income and financial assets, holdings by product and last login date
Passwords and trading PINsNot confirmed leakedLogin passwords and trading PINs — the information needed to place trades — have not been confirmed leaked

One reassurance has a limit. The login ID in the leak is separate from the Rakuten ID used across Rakuten Group services, which limits how far the exposed IDs reach. And the company says it has found no unauthorised logins or trades linked to the incident so far — but the investigation is still open, and "not found yet" is not the same as "will never happen".

rakuten securities data breach explained - Tokyo Stock Exchange main building entrance

Image: The entrance of the Tokyo Stock Exchange main building. Illustrative image — Rakuten Securities is Japan's largest online broker (Wikimedia Commons, Suicasmo, CC0).

Why it matters for India readers

Most Indian readers are not Rakuten Securities customers — it is a Japan-focused broker, and no India-specific impact has been reported. The warning for India is the pattern. Breaches now routinely reach customers through test systems and third-party providers rather than the front door: Uber's driver data breach via Fireworks AI and the Fireworks AI key leak that hit Cursor users followed the same shape, as did the Optimizely supply-chain attack that hit 178 websites.

The immediate risk is phishing. With names, phone numbers, email addresses and bank details in circulation, expect convincing messages impersonating Rakuten Securities — or any broker. Rakuten says its genuine emails contain no links and it never asks for personal or login details by phone, so any message that does either is suspect. The same rule holds for Indian brokers: no genuine broker asks for your password or OTP over a call or a link.

This is also the third Rakuten group disclosure this autumn: Rakuten Travel said in October that data of up to 2.6 million people who logged in may have leaked, and Rakuten Drive said files belonging to 15,382 accounts had been reachable for 231 days through stolen administrator credentials. Three group companies, three entry points — the common thread is basic hygiene around who can reach customer data and for how long.

Should you care?

If you hold a Rakuten Securities account, yes — check the company's notice, switch on passkey login and treat any "Rakuten" message with suspicion. If you don't, the direct risk is low, but the lesson applies to every broker account you hold: turn on the strongest login your broker offers, and never hand over a password or OTP to a caller or a link.

What Rakuten Securities customers should do now

Rakuten Securities says it has identified the affected customers and will contact each of them individually. Until then, the company's own advice is:

  • Do not trust unsolicited contact. The company's genuine emails contain no links, and it never asks for personal or login details by phone. Treat any email, text, call or letter claiming to come from Rakuten Securities or its group companies as suspect — do not click links or share details.
  • Set up passkey login. The company is making passkey login mandatory, and says more than 90% of customers who log in each day already use one. Passkeys use fingerprint or face recognition instead of a typed password.
  • Use the temporary block. Customers can temporarily block trading and withdrawals themselves from the security settings page after logging in — a useful option while the investigation continues.
  • Watch your accounts. Check recent logins and transactions, and watch for unfamiliar activity on the bank account registered for payouts.

FAQs

How many accounts were affected by the Rakuten Securities data breach?

Up to about 11.25 million accounts may have had branch and customer codes and login IDs exposed, and up to about 4.47 million accounts — including former customers — may have had detailed personal and financial data exposed. The two figures describe different data items, so they should not be added together.

Was my password leaked in the Rakuten Securities breach?

No leak of login passwords or trading PINs has been confirmed, and no unauthorised logins or trades linked to the incident have been identified so far. The login ID exposed is separate from the Rakuten ID used across Rakuten Group services.

What data was leaked in the Rakuten Securities breach?

For up to about 4.47 million accounts, the data that may have leaked includes names, dates of birth, addresses, phone numbers, email addresses, employers, payout bank account details, declared annual income and financial assets, and holdings by product. For up to about 11.25 million accounts, it is the branch and customer codes and login IDs.

What should Rakuten Securities customers do now?

Set up passkey login, which the company is making mandatory; treat any unsolicited message claiming to be from Rakuten as suspect; and use the security settings to temporarily block trading and withdrawals if you are concerned. The company says it will contact affected customers individually.

Takeaway

A test system held real customer records for Japan's biggest online broker — and it took five days to spot the leak. Passwords stayed safe this time; the next risk is the phishing wave that follows every breach like this.

If you hold a Rakuten Securities account, read the company's notice and switch on passkey login today — the link is in Sources below.

Sources

Rakuten Securities — Apology and notice regarding possible leakage of customer information (official notice, 17 November 2026)
NHK WORLD-JAPAN — Rakuten Securities warns of data leak for 4.47M accounts
CyberSIXT — Rakuten Securities data breach may have exposed 4.47M accounts
Tech in Japan — Japan's Autumn 2026 Data Breach Wave: What Is Going On and What Residents and Visitors Should Do

Comments