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 ↓
- Do not follow emails, SMS or calls claiming to be Rakuten Securities
- Set up passkey authentication
- Turn on the trading and withdrawal pause if you want it
3 more
- Never share your password; separate reused ones
- Watch notices and statements at your payout bank
- Use the individual notice and the contact number from the official site
- Where to verify (source)All sources ↓
- Rakuten Securities, "Apology and notice regarding possible leakage of customer information" (November 17, 2026; Japanese)
- 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
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).
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.
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.
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.
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.
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.
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).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.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.
- 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.
| Item | What the notice says | Status |
|---|---|---|
| Unauthorized access | Possible unauthorized access to some systems detected, blocked and fixed (November 16) | Confirmed (company) |
| Whether data was taken | Some information managed in a test-environment system may have been exposed on November 11 | Possible (company) |
| Branch and customer code, login ID | Up to about 11.25 million accounts | Possible (company) |
| Name, address, phone, email, payout account, etc. | Up to about 4.47 million accounts | Possible (company) |
| Former customers' information | Included | Possible (company) |
| Passwords, PINs and other information needed to trade | Leakage not confirmed | Not included (company) |
| Credit card numbers, My Number | Not mentioned in the notice | Not stated |
| Harm from misuse | No unauthorized access or trades believed caused by this incident confirmed (at the time of the notice) | Under investigation |
| Identifying affected customers | Completed; they will be told individually | Confirmed (company) |
| Cause and detailed course of events | Under investigation | Under 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.
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.
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.
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.
Read next
- A different Rakuten Securities incident (unauthorized access at a contractor; separate from this one): Unauthorized access at a digital-bond contractor
- Same type of case (including account details): Lashinbang unauthorized access
- Another brokerage case from the same period: Daiwa Securities contractor breach
- Preparing for follow-on scams: What is phishing / Smartphone security basics
- Protect your accounts: Choosing multi-factor authentication / Choosing a password manager
- Other 2026 incidents: Data breaches and cyberattacks (Japan and overseas)