Listen ↗

Cybersecurity · Article

Rakuten Securities Breach Hits Up to 15.7 Million Account Records After Real Customer Data Was Copied Into a Test System

Japan's online broker says an intruder may have taken names, income, assets and bank details for up to 4.47 million accounts from a test server holding unmasked production data. Passwords and PINs were not exposed.

Published · 7 min read

By Kaeleb Savon Heck

DAVAO DEL NORTE, Nov. 19, 2026 — Rakuten Securities, the online brokerage arm of Japan's Rakuten Group, says an intruder may have taken customer data tied to as many as 15.72 million account records, and the company has admitted that the data was sitting in a test system, unmasked, because it had copied real customer information there to check a system upgrade.

The Tokyo-based broker said on Nov. 17 that it detected possible unauthorized access on Nov. 16, blocked it and fixed the weak point. Its investigation found that data may have been taken out of the test environment on Nov. 11. For up to about 4.47 million accounts, the exposed records include names, birth dates, home addresses, phone numbers, email addresses, employers, the bank accounts customers use for withdrawals, and self-reported annual income and financial assets. For up to about 11.25 million accounts, the exposure is limited to branch and customer codes and login IDs.

The company says no login passwords or trading PINs leaked and that it has found no unauthorized logins or trades linked to the incident. But the breach is the largest yet in a wave of attacks on Japanese securities firms, and it has put a hard spotlight on a basic security rule that companies around the world break all the time: real customer data does not belong in a test environment.

What was exposed

According to the company's notice, as summarized by the incident tracker JapanHacked and by ITmedia NEWS, the data falls into two groups.

The larger group, up to about 11.25 million accounts, includes branch and customer codes and login IDs. Rakuten Securities says the login ID is separate from the Rakuten ID that customers use across the wider Rakuten ecosystem.

The smaller but more sensitive group, up to about 4.47 million accounts, adds names written in kanji and kana, dates of birth, addresses, phone numbers, email addresses, employers, withdrawal bank details (institution, account number and holder), self-reported annual income and financial assets, holdings by product type and last login dates. That group also includes the codes and login IDs.

ITmedia reported that the two groups together total up to about 15.72 million accounts, a figure TV Asahi also reported. The affected records include accounts that have already been closed.

The Japan Times reported that Rakuten Group shares fell more than 7% on Wednesday morning before recovering somewhat.

Why real data was in a test system

The question that has dominated Japanese social media is why customer records were in a test environment at all. Rakuten Securities answered it in an interview with ITmedia NEWS.

The company said that as part of an internal system upgrade, "some functions needed to be checked using production data." It said it copied part of the customer information from the production environment to a test server for a period of time to verify the upgrade, and that the data was not masked. It said test servers normally hold only dummy data and that this was an exceptional case.

The broker also stressed that this was not one employee acting alone. It said the copy went through the company's formal internal procedures. It said security measures were in place but that an attacker exploited a vulnerability. It declined to say when the real data was moved into the test system or how long the upgrade work lasted. Asked whether it had done the same thing in the past, it told ITmedia the chance was "not zero" but that it was almost never done and that this was a special case.

ITmedia noted that some social media users questioned why the period when real data was on the test server overlapped with the timing of the intrusion. The company has not said how the attacker got in, and its investigation is continuing.

How customers are being told

Rakuten Securities is directing customers to log in and check the notices screen to see whether their information may have been exposed. ITmedia reported criticism of that approach, since people have to log in to find out, and closed-account holders cannot.

The company told ITmedia that logging in is "basically required." It declined to say whether it would send individual emails, explaining that describing its notification method could help criminals craft phishing messages that impersonate it. For former customers who can no longer log in, it said it is notifying them "by some method."

The company is asking customers to switch to passkey login, which more than 90% of its daily users have already set up, and to consider using its option to temporarily suspend their own trading or withdrawals, according to JapanHacked and The Japan Times. The Japan Times reported that passkey login, based on the FIDO2 standard, will eventually become mandatory, though no date has been set.

Background: a hard year for Japan's brokers

The Japan Times described the incident as the largest so far in a series of attacks that have hit Japan since September. Last week, SMBC Nikko Securities reported a compromise of more than 56,000 accounts, with names, addresses, account numbers and balances exposed, the paper reported. Daiwa Securities, IwaiCosmo Securities and Sony Bank have faced leaks connected to outside service providers.

The Rakuten group itself has had a rough few months. The Japan Times reported that Rakuten Drive disclosed last month that photos, documents and other data from more than 15,000 accounts were exposed through unauthorized access between Jan. 29 and Sept. 17, and that Rakuten Travel reported two separate incidents in September and October that exposed names, emails and phone numbers tied to more than 2.6 million accounts.

The Japanese government announced a package of emergency cybersecurity measures earlier this month, according to The Japan Times, which linked the wave of attacks in part to hacking work being handed off to artificial intelligence. The Chronicle has previously reported on other major Japanese breaches this fall, including the Fugaku supercomputer intrusion and the Arara email breach.

Analysis: the test server problem

Security teams have a name for what Rakuten Securities did: using production data in non-production environments. It is common because it is convenient. Real data behaves like real data, with the odd names, long addresses and edge cases that fake records miss. But test systems tend to be less locked down, are touched by more people and tools, and get less monitoring. Copying millions of real records into one turns a lower-value target into a high-value one.

The standard defenses are well known. Teams can generate synthetic data, mask or tokenize sensitive fields, copy only the columns a test needs, keep copies for the shortest possible time, and give test environments the same access controls and monitoring as production when real data must be used. Rakuten Securities' own description, an unmasked copy approved through formal procedures, suggests the problem was not a rogue employee but a process that allowed it.

For customers, the most serious risk is probably not stolen trades, since passwords and PINs were not taken and passkeys are widely used. The bigger danger is targeted fraud. A leak that pairs names, addresses, employers, income, asset levels and bank details is exactly what scammers need to write convincing phishing emails or make phone calls pretending to be the broker, a bank or the police. That is one reason the company gave for not explaining how it will contact people.

What's next

Rakuten Securities says it has identified the affected customers and will contact them, and it continues to investigate how the attacker got in. Customers can check their status by logging in, set up passkey login, and use the self-service option to pause trading or withdrawals if they are worried.

Anyone with a Rakuten Securities account, current or closed, should treat unexpected calls, texts or emails that mention their account, income or bank details with suspicion, and should reach the company only through its official app or website rather than through links in messages.

The company has not said when its investigation will conclude or whether regulators have opened their own inquiries.

Sources

Return to all Chronicle publications

Continue reading

No saved reading progress on this device.

Keep the connection.

LET’S MAKE
SOMETHING. ↗

Listen

Playback and availability are provided by Apple Music.