Nearly 16 million customer accounts at Rakuten Securities may have had identifying data exposed after the Tokyo-headquartered brokerage discovered unauthorized access to its systems, the firm disclosed on November 17.
Breach timeline and discovery
Rakuten Securities, part of the Rakuten Group, apologized to customers on November 17 and said it first discovered unauthorized access to its systems the day before. The company also disclosed that “on Wednesday, November 11 some information managed within our test environment system may have been leaked to an external party.” Rakuten said it is “continuing our investigation into the cause and detailed circumstances of the unauthorized access.”
Scope and types of data exposed
Rakuten Securities said the incident could affect nearly 16 million accounts in two groups. For around 4.47 million accounts, the firm reported that branch/customer code, login ID, name, date of birth, address, phone number, email address, employer, withdrawal account details, annual income, asset information, and last login date were compromised. A further 11.25 million accounts had branch/customer code and login IDs taken.
The company confirmed that passwords, PINs and other information were not taken and that there was “no sign of unauthorized access to customer accounts.” Rakuten has warned customers to expect follow-on phishing attempts, which it described as efforts “presumably trying to trick individuals into handing over their logins.”

This site is the portfolio.
OSINTSights runs on Cloudflare Workers, D1, R2, and Vectorize, with an AI pipeline on Hetzner ARM. Nubivance designed, built, and operates it. We do the same for clients.
See what we buildWhy using production data in test environments matters — John Strand
Security experts questioned Rakuten Securities’ use of production data in a test environment. John Strand, owner of Black Hills Information Security, criticised the practice: “This isn’t some advanced security concept or something that requires sophisticated technology to address. It’s one of the most fundamental rules of protecting sensitive information, and yet we continue to see organizations make these mistakes.” He added, “The proper way to do this is to have separate development, testing, and staging environments, each with clearly defined security controls.”
Rakuten’s advice and its push for passkeys
Facing the risk of credential theft and phishing, Rakuten Securities urged customers who do not yet use passkeys to switch. The firm said that more than 90% of its customers currently log in using phishing-resistant passkeys, and encouraged the remainder to adopt them “to mitigate the risk of account takeover.”
Rakuten’s notice framed the immediate threat as social-engineering attempts that may follow the data exposure, not an ongoing compromise of account credentials according to the firm’s statement that passwords and PINs were not taken.
What this means for technologists, customers, and regulators
- Technologists and security teams: The incident highlights issues around environment separation and data handling. Strand’s comment points to a remedial focus on segregating production data from test systems and implementing distinct security controls for development and staging environments.
- Customers and retail investors: Millions of account holders face heightened phishing risk. Rakuten has stressed that most customers already use passkeys and has urged the remainder to switch; customers should be alert to follow-on contact attempts designed to harvest login credentials.
- Regulators and market overseers: The disclosure arrives after a prior warning from the Financial Services Agency (FSA) about a sharp increase in account hijacking at Japanese securities companies, where hackers made illegal trades of over 304 billion yen ($2bn). Regulators will see the Rakuten incident in the broader context of recent widespread breaches affecting Japanese companies.
The Rakuten Securities breach lands at the end of a year that has already seen a string of data exposures and extortion incidents in Japan, including breaches reported at Burger King (11 million customers), Times Car (6.6 million), Daiichi Kosho (8 million), Yakiniku King (11 million), and an October incident in which GMO told customers to disconnect virtual desktops after a ransomware actor accessed them. Rakuten’s ongoing investigation will focus on “the cause and detailed circumstances” of the November 11 leak from its test environment — a finding that raises hard questions about why production-style data were present in testing and what controls will be applied to prevent a repeat.
Original reporting: https://www.infosecurity-magazine.com/news/rakuten-securities-breach-15/




