Subscribe
0%
Illustration for: Rakuten Securities breach exposed up to 15.7M accounts via a test server holding real customer data. What to do

Rakuten Securities breach exposed up to 15.7M accounts via a test server holding real customer data. What to do

Japan's Rakuten Securities says attackers reached a test system loaded with unmasked production data, exposing login IDs for up to 11.25 million accounts and income, bank and asset details for up to 4.47 million more. Rakuten Bank shares plunged on November 18. Customers should switch on passkeys and watch for impersonation scams.

Listen to this article0:00 / 4:05

Rakuten Securities, a Japanese online broker with about 15 million accounts according to BigGo Finance, says an intruder reached an internal test environment that held real customer data, and personal information on up to 4.47 million accounts has leaked. The company announced the breach on November 17. On November 18 it confirmed that data had left the company and explained why production records were on a test server, according to ASCII.jp and BigGo Finance.

Why it matters: this is not just names and emails. The detailed set includes bank account numbers used for withdrawals, self-reported annual income, employer and holdings by product. That is exactly what makes investment-fraud calls convincing. The cause is also a common shortcut: copying live data into a test system without masking it.

What leaked

Rakuten split affected accounts into two groups that do not overlap. Both include customers who have already closed their accounts.

Group Data Accounts (up to)
Basic Branch code, customer code, securities login ID ~11.25 million
Detailed All of the above, plus name, date of birth, address, phone, email, employer, withdrawal bank account details, declared annual income, financial assets and holdings by product, last login date ~4.47 million
Total ~15.72 million

BigGo notes that the 15.72 million total is a sum of the two groups, not a figure Rakuten stated directly. Securities login IDs are separate from general Rakuten IDs. Rakuten says it has not confirmed any leak of passwords or trading PINs and has found no unauthorised logins or trades so far.

How it happened

According to both outlets, the test environment normally used dummy data. An internal system upgrade needed some functions checked against production data, so part of the live customer data was copied to the test server, unmasked, for a period. Rakuten says data may have been taken out from November 11. It detected the access on November 16 and blocked it. It has not said who the attacker was or how they got in, and says the investigation is continuing.

Bloomberg Intelligence analyst Michael Makdad, quoted by The Star, said the key question is "why identifiable customer information was held there." This is Rakuten Securities' second incident in weeks. BigGo reports an October 31 disclosure of a 362-record leak of bond buyers through a subcontractor's system.

Market reaction

Rakuten Bank, which now owns the brokerage, fell sharply in Tokyo on November 18. The Star (Bloomberg) says it dropped 19% to its daily limit, its biggest intraday fall since its 2023 listing. BigGo gives a closing loss of 15.16% at 4,489 yen. Parent Rakuten Group fell as much as 7.5%. The Star adds that SMBC Nikko and Daiwa have also reported data leaks in recent weeks.

What customers should do

Rakuten says it will contact affected customers individually. You can also check the Notifications screen after logging in. Its advice, per BigGo and ASCII.jp:

  1. Turn on passkey login. Rakuten says over 90% of regular users already have. Users without one must authenticate with a one-time key first. That process was delayed on November 18, so retry if it fails.
  2. Consider pausing trades and withdrawals from the security settings page if you don't need them right now.
  3. Treat calls, SMS and emails "from Rakuten" as hostile. The company says its emails contain no URLs and it never asks for login details or personal information by phone.
  4. Expect targeted fraud. Anyone who knows your income, employer and holdings can write a very believable pitch. Be especially sceptical of investment offers and "account security" calls in the coming months.

The lesson for everyone else

If your team ever loads production data into staging "just for this upgrade", this is the cost. Mask or tokenise the data, put an expiry on the copy, and give the test system the same access controls and monitoring as production.

Sources

  1. ASCII.jp — Rakuten Securities: Up to 15.72 Million Accounts Potentially Leaked, Real Customer Data Found in Test Environment ascii.jp
  2. BigGo Finance — Rakuten Securities Hit by Unauthorized Access; Login IDs of Up to 11.25 Million Accounts May Leak, Income and Asset Data Affected for 4.47 Million finance.biggo.com
  3. The Star (Bloomberg) — Rakuten Bank shares tank as securities arm faces data breach thestar.com.my

#Rakuten#Rakuten Securities#Rakuten Bank#data breach#Japan#passkeys#phishing