TOKYO, November 19, 2026. Japan’s Financial Services Agency has ordered Rakuten Securities to submit a report following a major potential data exposure involving the brokerage’s testing environment. The company confirmed receipt of the order on November 19 under provisions of the Financial Instruments and Exchange Act and the Act on the Protection of Personal Information.
The order follows a November 17 company notice describing suspected unauthorized access to a system used for testing. Rakuten says access was detected on November 16 and that information stored in the test environment may have been taken out on November 11. Investigators have not publicly established the entry method or the full extent of confirmed theft.
Which customer records may be affected
Rakuten’s notice identifies two categories of potentially exposed information. One covers up to approximately 4.47 million accounts and may include identifying information, contact details, workplace, designated bank-account details, declared income and assets, investment holdings, a login ID and the date of the last login. A separate category lists up to approximately 11.25 million accounts with branch/customer codes and login IDs.
These are the company’s maximum counts for two information categories; it has not publicly proved that adding them yields 15.72 million distinct individuals. Importantly, the brokerage says it has not confirmed exposure of the passwords and transaction PINs needed to trade, and has not identified unauthorized transactions attributable to this incident as of its statements.
Why a test environment was holding production data
Japanese reporting based on company comment indicates that customer data had been copied into a test environment for an internal system upgrade requiring checks against real data. That operational decision deserves scrutiny. Nonproduction systems sometimes have different access paths, longer retention periods or weaker monitoring than systems used to run financial transactions.
Using live personally identifiable information for testing can expand the blast radius when a test system fails. Financial institutions can reduce that risk with masking, synthetic records, tightly controlled exceptions, separate identities and equal-or-stronger protection for any nonproduction environment that genuinely must contain production data.
What the regulatory order means
The new reporting requirement demands further examination, not a public finding that every potentially exposed record was actually stolen or that particular data-security laws were violated. Rakuten says it will continue establishing the facts, analyzing causes and developing recurrence-prevention measures. The company’s response and the regulator’s subsequent conclusions may clarify questions the initial notice cannot.
Guidance to customers
Rakuten warns about calls, emails, SMS and physical mail impersonating the brokerage. Its notice states that routine customer emails from the firm do not contain URLs and that callers will not request login secrets. Customers should navigate through the official app or a previously saved website address, review account activity, and use passkeys if offered. A caller’s knowledge of holdings, address or branch code is not proof of legitimacy.
Primary sources
Rakuten Securities, November 19 statement acknowledging the Financial Services Agency reporting order (Japanese PDF); Rakuten Securities November 17 customer notice (Japanese); ITmedia, November 18 — company explanation of production data in testing.