Security Guides

Rakuten Securities unauthorized access (up to about 11.25 million accounts): names, addresses and payout bank details may have leaked — what customers should do

Rakuten Securities says test-environment data may have leaked: login IDs for up to 11.25M accounts, addresses and payout accounts for up to 4.47M. Passwords not confirmed leaked.

Published 2026-11-19 Updated 2026-11-19 Last verified 2026-11-19 10 min read
On this page

For: anyone who has or had a Rakuten Securities account (including closed accounts), and anyone who runs a brokerage or financial service. This article is based on Rakuten Securities' official notice and does not cover attack methods.

Developing: this article will be updated as the organisation publishes more

Who is affected

anyone who has or had a Rakuten Securities account (including closed accounts), and anyone who runs a brokerage or financial service.

Confirmed so farSee the table ↓
  • Unauthorized access
  • Identifying affected customers

Listed as possibly affected

  • Whether data was taken
  • Branch and customer code, login ID
  • Name, address, phone, email, payout account, etc.
1 more
  • Former customers' information
Not yet confirmed
  • Cause and course of events
  • Whether data was actually taken
  • Measures to prevent recurrence
What to do nowSee the steps ↓
  1. Do not follow emails, SMS or calls claiming to be Rakuten Securities
  2. Set up passkey authentication
  3. Turn on the trading and withdrawal pause if you want it
3 more
  1. Never share your password; separate reused ones
  2. Watch notices and statements at your payout bank
  3. Use the individual notice and the contact number from the official site
Last checked
As of November 19, 2026
Follow-up plans and what we checked

In its November 17 notice, Rakuten Securities says the cause and detailed course of events are still under investigation and that it will contact customers again if there is anything new to report. As of November 19, no follow-up was found on the company's official site.

What customers should do today

1

Do not follow emails, SMS or calls claiming to be Rakuten Securities

The items that may have leaked include name, date of birth, address, phone number, email address and employer. Together they let someone write a convincing message with the right name and address.

If a message about an account check, a re-registration for security or an apology arrives, do not open the link. Open the app or official site yourself instead. The company says its emails contain no URLs and that it never asks for personal or login details by phone (how to tell fakes: What is phishing).

2

Set up passkey authentication

The company is making passkey login mandatory because it resists unauthorized access and phishing, and asks customers who have not set one up to do so. It says more than 90% of customers who log in each day already use it.

A passkey makes it hard to steal credentials by getting you to type them into a fake site. For how multi-factor options compare, see Choosing multi-factor authentication.

3

Turn on the trading and withdrawal pause if you want it

The company says customers can temporarily suspend trading and withdrawals themselves from the security settings page after logging in. Consider it for accounts you will not use for a while, or if you are worried.

Do this from the official app or site that you open yourself, not from a search result or a link you received.

4

Never share your password; separate reused ones

The company says it has not confirmed leakage of passwords or PINs, and the notice does not tell customers to change them now. Login IDs may have leaked, however, so if you reuse the same password elsewhere, it is safer to separate them.

A password manager is the practical way to audit reuse. To see whether a password appeared in earlier leaks, see How to check if your password leaked.

5

Watch notices and statements at your payout bank

The items that may have leaked include the institution, account number and holder of your payout bank account. An account number alone does not allow a transaction, but it can make a fake message sound credible. Check your bank's alerts and statements, and contact the bank and Rakuten Securities about anything you do not recognise.

6

Use the individual notice and the contact number from the official site

The company says it has finished identifying the customers whose data was confirmed to be affected and will report to them individually. When one arrives, check it against the official notice page rather than clicking its links.

The contact point is the Rakuten Securities Customer Support Center (toll-free 0120-862-274; weekdays 8:30 to 17:00, weekends 9:00 to 17:00 JST). Use the number on the official site, not one written in a message you received.

What happened (from Rakuten Securities' notice)

Rakuten Securities published an apology and notice about possible leakage of customer information on November 17, 2026. Everything below is based on the company's statement.

  1. November 11, 2026 (Wed)

    Some information managed inside a test-environment system may have been exposed to the outside (a date confirmed by the investigation).
  2. November 16 (Mon)

    The company detected possible unauthorized access by a third party to some systems, blocked access to the affected part and applied fixes.
  3. November 17 (Tue)

    Published the notice. It says it has identified the customers whose data was confirmed to be affected and will report to them individually.
Up to about 11.25M accounts
Branch and customer codes, login IDs
Up to about 4.47M accounts
Range that also includes names, addresses, payout accounts
Not confirmed
Leakage of passwords or PINs
Not confirmed
Unauthorized access or trades believed caused by this incident (at the time of the notice)
Information that may have been taken (from Rakuten Securities' notice)
Who
Information on customers who registered with Rakuten Securities, including customers who closed their accounts
Items for up to about 4.47M accounts
Branch and customer code, login ID, name, kana name, date of birth, address, phone number, email address, employer, payout bank account (institution, account number, holder), income and financial assets as declared by the customer, per-product asset information, last login date
Items for up to about 11.25M accounts
Branch and customer code, login ID (the company says this is different from the Rakuten ID)
Not confirmed as leaked
Passwords needed to log in to Rakuten Securities, PINs and other information needed to trade
Harm
At the time of the notice, no unauthorized access or unauthorized trades believed to be caused by this incident had been confirmed
Cause
The cause and detailed course of events are under investigation
Notice to customers
Customers confirmed to be affected will be told individually

Reading the numbers: do not add the two account counts

The notice gives two figures: up to about 11.25 million accounts (branch and customer codes and login IDs) and up to about 4.47 million accounts (the longer list including names and addresses). They are per-item ceilings, and the company writes "up to". Do not add them together or read either as a number of people; they are counts of accounts.

What is known and what is not

As of November 19, 2026 (reflecting the notice of November 17). When the company publishes more, this table will be rewritten.

ItemWhat the notice saysStatus
Unauthorized accessPossible unauthorized access to some systems detected, blocked and fixed (November 16)Confirmed (company)
Whether data was takenSome information managed in a test-environment system may have been exposed on November 11Possible (company)
Branch and customer code, login IDUp to about 11.25 million accountsPossible (company)
Name, address, phone, email, payout account, etc.Up to about 4.47 million accountsPossible (company)
Former customers' informationIncludedPossible (company)
Passwords, PINs and other information needed to tradeLeakage not confirmedNot included (company)
Credit card numbers, My NumberNot mentioned in the noticeNot stated
Harm from misuseNo unauthorized access or trades believed caused by this incident confirmed (at the time of the notice)Under investigation
Identifying affected customersCompleted; they will be told individuallyConfirmed (company)
Cause and detailed course of eventsUnder investigationUnder investigation

What names, addresses and payout accounts can be used for

In general, a name, address, phone number and email address together make a convincing fake message possible. Here, employer, declared income and financial assets, payout account and per-product assets may be added. This does not mean any of this happened in this incident; it is what can generally happen.

  • Fake messages posing as a brokerage: an email or SMS with the right login ID and name is hard to tell from a real one. The typical aim is to get you to type a password or PIN on a linked page.
  • Calls or pitches that claim to know your assets: if declared income, financial assets or per-product holdings are known, an investment pitch or scam can pretend to "know your account".
  • Messages posing as a bank or public body: knowing the payout bank and account holder makes a message in that bank's name more convincing.

This differs from incidents where login credentials themselves were stolen; here the company has not confirmed leakage of passwords or PINs. For another case involving account details and ID documents, see the Lashinbang breach.

For people who run a brokerage or financial service

This is limited to what the notice shows. The cause is under investigation, so the entry point is not discussed here.

1

Check what data sits in test environments

According to the notice, the information that may have been exposed was "managed inside a test-environment system". It covers current and former customers and may include addresses and payout accounts.

In general, test environments tend to be protected less strictly than production. Ask whether real customer data is in your test environments; if it must be, give it the same controls as production (access limits, logging, multi-factor authentication), or see whether the design can avoid real data.

2

Decide how long you keep former customers' data

The notice says former customers' information is included. How long records must be kept differs by business and law. Separate items you must keep from those you no longer need, and delete or anonymise the latter, to shrink the impact of any leak.

3

Break the impact down by item when you announce it

The company published separate figures for the up to about 11.25 million account items and the up to about 4.47 million account items. Showing items and counts separately lets users judge their own exposure. Using the same wording in individual notices and on the website matters too.

Sources (public record)

The facts in this article rest on the public information below. Causes and methods that have not been published are not speculated about.

  • Rakuten Securities, "Apology and notice regarding possible leakage of customer information" (November 17, 2026; Japanese) — rakuten-sec.co.jp

Update history

2026-11-19: First version, based on the company's November 17 notice. As of November 19, no follow-up was found on the company's official site. This article will be updated when the cause and course of events are published.

Latest breaking reports

All breaking reports →

FAQ

QWhat was exposed in the Rakuten Securities breach?
A

According to Rakuten Securities' November 17, 2026 notice, branch and customer codes and login IDs (up to about 11.25 million accounts) may have been taken. For up to about 4.47 million accounts, the list also includes name, kana name, date of birth, address, phone number, email address, employer, payout bank account (institution, account number, holder), self-declared income and financial assets, per-product asset information and last login date. Information on former customers is included.

QAm I affected?
A

The company says it has finished identifying the customers whose data was confirmed to be affected and will report to them individually. Anyone who held a Rakuten Securities account, including closed accounts, may be affected, so wait for the individual message and check the official notice page. The company says its emails contain no URLs.

QWere passwords or PINs leaked?
A

The company says it has not confirmed leakage of the passwords, PINs or other information needed to trade. It also says that, at the time of the notice, it had not confirmed unauthorized access or unauthorized trades believed to be caused by this incident. Login IDs may have leaked. The company asks customers who have not yet set up passkey authentication to do so.

QWhat was the cause?
A

It has not been published. The company says the cause and detailed course of events are still under investigation. It says it detected possible unauthorized access on November 16 and confirmed that some information managed in a test-environment system may have been exposed on November 11.

QWhat should I do if someone claiming to be Rakuten Securities contacts me?
A

Do not open the link and do not give personal or login details by phone. The company says its emails do not contain URLs and that it never asks for personal or login information by phone. Check through the official app or site you open yourself, or through the customer support number listed on the official site.

QCan I pause trading or withdrawals?
A

The company says customers can set a temporary suspension of trading and withdrawals themselves from the security settings page after logging in. It also asks customers who have not set up passkey authentication to do so. Check the official guides for the steps.