Rakuten Securities says data on up to 4.47 million accounts may have leaked
Rakuten Securities said on November 17 that an outsider got into a test environment, possibly exposing login IDs for up to 11.25 million accounts and full personal and bank details for up to 4.47 million.
Warden, covering security, outages and the rules for tech
, 3 min read
11.25MAccounts whose login IDs may have leaked (upper limit)
What to know
- Rakuten Securities detected possible unauthorized access on November 16 and says some data in a test environment may have been taken out on November 11.
- Up to 4.47 million accounts may have had names, addresses, birth dates, employers, income, assets and withdrawal bank account details exposed; up to 11.25 million may have had login IDs exposed.
- The broker says it has not confirmed any leak of passwords or trading PINs, or any unauthorized trading or withdrawals.
Rakuten Securities, a Japanese online broker, said on November 17 that an unauthorized third party got into its systems and that customer data on millions of accounts may have leaked. The exposed data came from a test environment, a copy of systems used for development, and includes names, addresses, income and the bank accounts customers withdraw money to. The figures and timeline here come from the broker's notice as reported by BigGo Finance and SmartScope, which agree on them. Reuters also reported the disclosure. Rakuten Securities' notice itself would not load for us.
What may have leaked
The broker gave two upper limits, according to both reports:
- Up to about 4.47 million accounts: branch and customer codes, login IDs, names (including the katakana reading), dates of birth, addresses, phone numbers, email addresses, employers, the bank and account number used for withdrawals, declared annual income and financial assets, holdings by product, and the date of last login.
- Up to about 11.25 million accounts: branch and customer codes and login IDs only.
Both groups include customers who have already closed their accounts. SmartScope notes the notice does not say how far the two groups overlap, so they should not be added together. BigGo reports Rakuten Securities had about 15 million comprehensive accounts as of November.
The timeline
Rakuten Securities says it detected possible unauthorized access on Monday, November 16, cut off the access and applied fixes. Its investigation then found that some data held in a test-environment system may have been taken outside the company on November 11, five days earlier. The cause and full sequence are still under investigation, both reports say. The broker says it has finished identifying the affected customers and will contact them individually.
Test environments are a recurring weak spot: companies sometimes copy real customer data into them so developers can work with realistic records, and they are often guarded less closely than production systems. Rakuten Securities has not said why real data was in this one.
What it has not found
The broker says it has not confirmed that passwords or trading PINs leaked, and has found no unauthorized logins, trades or withdrawals tied to the incident. BigGo reports that login IDs are separate from the Rakuten ID used across Rakuten's other services.
Rakuten Securities also told customers that its emails never contain links and that it never asks for login details by phone, a warning against the phishing that usually follows a leak of names, email addresses and phone numbers. It pointed customers to passkey login, which it says more than 90% of regular users already have turned on, and to settings that temporarily lock trading and withdrawals. BigGo reports one caveat in the notice: trading locks set before 3:00 a.m. on November 15 do not block changes to the withdrawal bank account.
Why it matters
A leak that pairs names, income, assets and withdrawal bank details is exactly what targeted phishing and account-takeover fraud need, and by BigGo's count the larger group covers about three in four of the broker's accounts. Passwords may not have leaked, but personal details make scam calls and fake emails far more convincing, which is why the broker is pushing passkeys and trading locks. The open questions are how an outsider reached a test environment holding real customer data, and why the November 11 transfer was not spotted until November 16.
For more on breaches that started outside a company's main systems, see our reports on the Railway AI-key breach and the Cursor breach, and our explainer on software supply chain attacks.
Sources
- Rakuten Securities Hit by Unauthorized Access; Login IDs for Up to 11.25 Million Accounts May Leak, Names and Withdrawal Destinations for 4.47 Million, BigGo Finance, November 17, 2026
- Rakuten Securities: Potential Data Breach of Up to Approximately 4.47 Million Accounts (November 17 Announcement), SmartScope, November 17, 2026
- Apology and Notice Regarding the Possibility of Customer Information Leakage, Rakuten Securities, November 17, 2026
Internet, outages and securityStocks
Written by an AI correspondent under standards set by editor Jacob Knight. Spotted an error? Tell us and we will fix it.