Rakuten Securities Breach Exposes Data on Millions, and a Test Environment Is the Weak Spot
Rakuten Securities, one of Japan's leading online brokerages, has disclosed a major breach that could affect nearly 16 million people. The Tokyo-based firm lets retail investors trade stocks, bonds, foreign exchange and other financial products. It is part of the Rakuten Group.
The company apologised to customers on November 17, saying it discovered unauthorised access to its systems the day before. Its investigation found that on November 11, some information held in a test environment may have been leaked to an external party. The cause and detailed circumstances are still under investigation.
About 4.47 million accounts had a wide range of details exposed: branch and 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. A further 11.25 million accounts had only their branch or customer code and login ID taken. The firm says passwords, PINs and other information were not stolen, and it has seen no sign of unauthorised access to customer accounts.
Security experts questioned why production data was in a test environment at all. John Strand of Black Hills Information Security called it a fundamental rule of protecting sensitive information, and said organisations should keep separate development, testing and staging environments, each with clearly defined security controls.
Rakuten Securities has warned customers to expect follow-on phishing attempts aimed at stealing logins. Over 90% of customers already sign in with phishing-resistant passkeys, and the company urged the rest to switch. The breach follows a regulator warning last year about a sharp rise in account hijacking at Japanese securities firms, and a string of other large breaches at Japanese companies this year.
Why it matters
The breach hit a test environment, so any business that copies live customer records into development or testing systems, where controls are often weaker, faces the same exposure. Even without passwords, the stolen identity and financial details give attackers strong material for convincing phishing, so protection of the login itself becomes the deciding control. Rakuten's high passkey uptake shows why phishing-resistant authentication limits the damage when personal data leaks.
What to do
- Audit test, development and staging systems for copies of real customer data.
- Separate development, testing and staging environments, each with its own defined security controls.
- Enable phishing-resistant passkeys for customer and staff logins where available.
- Warn customers and staff to expect phishing messages that use leaked personal details.