---
title: "Rakuten Securities: up to 4.47m accounts’ data may have leaked from a test system"
summary: "Rakuten Securities’ notice of 17 November: what may have left a test system on 11 November, the 11.25m login IDs, why test data matters, and what customers should do."
url: https://www.thetechbag.com/blog/rakuten-securities-4-47m-accounts-test-environment
format: Note
desk: "Security"
area: "Threats & vulnerabilities"
region: Global
published: 2026-11-21
facts_checked: 2026-11-21
author: TechBag (The TechBag Journal)
tags: ["Rakuten Securities data leak","Rakuten Securities breach","楽天証券 情報漏えい","Rakuten Securities unauthorised access","Rakuten Securities","test environment","test data","Personal Information Protection Commission","passkeys","FIDO2","Japan data breach","ARARA","NTT Data","Minkabu","phishing","financial sector breaches"]
cover: https://www.thetechbag.com/blog/covers/rakuten-securities-4-47m-accounts-test-environment.png
---

# Rakuten Securities: up to 4.47m accounts’ data may have leaked from a test system

*Rakuten Securities’ notice of 17 November: what may have left a test system on 11 November, the 11.25m login IDs, why test data matters, and what customers should do.*

Note · Security · Threats & vulnerabilities · By TechBag · Published 2026-11-21 · Facts checked 2026-11-21 · Canonical: https://www.thetechbag.com/blog/rakuten-securities-4-47m-accounts-test-environment

Names, addresses, withdrawal bank accounts, self-declared income and financial assets, and holdings for up to about 4.47 million Rakuten Securities accounts may have leaked from one of the Japanese online broker’s test environments, the company said on 17 November.[1] The customer code and login ID of up to about 11.25 million accounts may also have gone. Rakuten Securities detected possible unauthorised access on Monday 16 November, cut off access and fixed the affected part of its systems; its investigation then showed that data held in a test environment may have leaked on Wednesday 11 November. It has found no leak of passwords, PINs or anything else needed to trade, and no unauthorised log-ins or trades linked to the incident. How the attackers got in is still under investigation.[1]

4.47m

accounts whose name, address, withdrawal account, income and assets may have leaked (up to about)

Rakuten Securities

11.25m

accounts whose customer code and login ID may have leaked (up to about)

Rakuten Securities

5 days

from the possible leak on 11 November to detection on 16 November

Rakuten Securities

90%+

of customers who log in daily already use passkeys, which Rakuten is making compulsory

Rakuten Securities

## What may have left, and what did not

Rakuten lists two groups. For up to about 4.47 million accounts: branch and customer code, login ID, name in kanji and kana, date of birth, address, phone number, email address, employer, the bank account withdrawals are paid to (bank, account number and holder), annual income and financial assets as the customer declared them, assets held by product, and the date of the last log-in. For up to about 11.25 million accounts: the branch and customer code and the login ID. Both groups include customers who have closed their accounts, and the login ID is not the Rakuten ID used across the group’s other services.[1] Rakuten does not say whether the larger group contains the smaller one, so the two figures are not added. It says it has identified every affected customer and will write to each.[1]

The combination is what makes such a record valuable to a fraudster: a login ID, a real name, a phone number and knowledge of how much someone holds lets a fake “security check” call or email sound genuine. That is why Rakuten’s advice is about contact, not passwords.

## Why a test environment held customers’ data

A test environment is a copy of a system where new code is tried before it goes live, and it is often guarded less closely than the live system. Japan’s Personal Information Protection Commission lists, among the measures that prevent leaks, prohibiting the use of personal data as test data, or replacing part of it with other data, so that test data holds as little personal data as possible.[2] Rakuten has not said why real records were in its test system.

ReportedRegulators elsewhere point at the same door

South Korea’s Financial Services Commission, ordering an inspection of about 580 financial firms on 5 November, named development, test and temporary-operation systems among “the systems where recent breaches have mainly occurred” (our translation).[3] In India, CERT-In’s advisory of 4 November describes “Internet-exposed non-production environments (UAT/staging/testing) used as entry points” and asks firms to isolate them from production, with “no shared credentials, tokens, API keys, databases or direct network paths”.[4] The Journal’s reading of [Korea’s 40 hacks at 37 financial firms](https://www.thetechbag.com/blog/korea-40-hacks-37-financial-firms) covers that wave.

## The broker’s third notice in under three weeks

Two earlier notices concerned suppliers, not Rakuten’s own systems. On 31 October it reported that a platform run by a contractor of NTT Data, used for bonds sold with digital perks, may have exposed 362 customer records. On 5 November it reported that 2,109 email addresses registered for an economic-indicator alert may have leaked from ARARA, the mailing firm used by its provider Minkabu.[5][6] That was the breach in our analysis of [ARARA’s 81.3 million addresses](https://www.thetechbag.com/blog/arara-81-million-email-addresses-380-clients-japan).

**Figure: Rakuten Securities’ third leak notice in under three weeks was the first from its own systems**

*Dates of each possible leak, its discovery and Rakuten Securities’ notices, 27 October to 17 November 2026 (Japan time)*

| Date | Event | Detail |
| --- | --- | --- |
| 27 Oct 2026 | ARARA break-in | At the mailing firm behind an alert email |
| 31 Oct 2026 | Notice 1: 362 records | Via an NTT Data contractor’s platform |
| 5 Nov 2026 | Notice 2: 2,109 emails | Via Minkabu’s mailer, ARARA |
| 11 Nov 2026 | Test-environment data may leak | Found only in the later investigation |
| 16 Nov 2026 | Possible intrusion detected | Access cut off and the system fixed |
| 17 Nov 2026 | Notice 3: up to 4.47m accounts | Login IDs of up to 11.25m |

Source: Rakuten Securities, notices of 31 October, 5 November and 17 November 2026 · as of 17 November 2026

What customers are told to do: Rakuten’s emails carry no links, and it never asks for personal or log-in details by phone; treat any message or call that does as fake. Set up passkey (FIDO2) log-in, which Rakuten is making compulsory and which more than 90% of customers who log in daily already use. Customers can also suspend trading and withdrawals themselves from the security settings page.[1] Our note on [Shonan Beauty Clinic’s 1.62m customers](https://www.thetechbag.com/blog/sbc-medical-shonan-beauty-1-62m-customers-breach) and the [KARTE breach](https://www.thetechbag.com/blog/karte-breach-570-companies-mufg-6-5m-customers) cover Japan’s other large leaks this month.

How we did this

Figures as of 21 November 2026, 9pm IST

Every incident figure is Rakuten Securities’ own, from its Japanese notice of 17 November; translations are ours. Rakuten writes that the data “may have leaked outside” (漏えいしたおそれ) and lists it as information that “may have been taken outside”; it does not say the data was taken, and neither do we. Both counts are Rakuten’s “up to about” (最大約) figures and include closed accounts, so they are not a share of current customers. “5 days” (11 to 16 November) and “under three weeks” (31 October to 17 November) are our arithmetic. We checked Rakuten’s notices list at about 8pm IST on 21 November and found no update. Why such data helps a fraudster, and that test systems are often guarded less closely, is our reading, not Rakuten’s.

Spotted an error? Write to us; corrections are published at the foot of the piece.

Sources

1. [Rakuten Securities, 当社お客様の情報漏えいの可能性に関するお詫びとお知らせ (apology and notice on a possible leak of customer information), in Japanese](https://www.rakuten-sec.co.jp/web/info/info20261117-02.html) — 17 November 2026
2. [Personal Information Protection Commission, Q&A 10-21 on the general guidelines: measures to prevent leaks through information systems, in Japanese](https://www.ppc.go.jp/all_faq_index/faq1-q10-21/) — undated page
3. [Financial Services Commission (Korea), release on the sector-wide meeting on security in the AI era, in Korean](https://www.fsc.go.kr/no010101/88086) — 5 November 2026
4. [CERT-In, advisory CIAD-2026-0058: Escalation of AI-Driven Attacks on BFSI Entities](https://www.cert-in.org.in/s2cMainServlet?pageid=PUBVLNOTES02&amp;VLCODE=CIAD-2026-0058) — 4 November 2026
5. [Rakuten Securities, 外部サービス提供元への不正アクセスによるお客様情報漏えいの可能性について (possible leak through an external service provider), in Japanese](https://www.rakuten-sec.co.jp/web/info/info20261031-01.html) — 31 October 2026
6. [Rakuten Securities, 委託先への不正アクセスによるメールアドレスの漏えいの可能性について (possible leak of email addresses through a contractor), in Japanese](https://www.rakuten-sec.co.jp/web/info/info20261105-01.html) — 5 November 2026

**Disclosure.** TechBag is a software reseller: it earns when companies buy through it, including from vendors named here. The analysis is TechBag’s own; no vendor paid for or saw this piece before publication. Facts are labelled reported, TechBag count or our view.

**Read this next:** [KARTE breach leaked customer data from 570 companies, 6.5m at MUFG Bank](https://www.thetechbag.com/blog/karte-breach-570-companies-mufg-6-5m-customers) — Japan’s other leak this month: the KARTE breach reached customer data at 570 companies, 6.5m of them MUFG Bank’s, through one marketing platform.

Go deeper on TechBag

- [Japan’s ARARA lost 81.3 million email addresses from up to 380 clients](https://www.thetechbag.com/blog/arara-81-million-email-addresses-380-clients-japan) — the mailing-firm breach behind Rakuten Securities’ notice of 5 November
- [40 hacks at 37 Korean financial firms in five weeks; regulator to inspect 580](https://www.thetechbag.com/blog/korea-40-hacks-37-financial-firms) — Korea’s regulator names development and test systems among the breached
- [Data security posture management guide](https://www.thetechbag.com/browse/data-security-privacy/dspm) — finding where copies of customer data sit, test systems included
