Rakuten Securities test-environment intrusion

Rakuten Securities reported possible customer-data exposure from a test environment, with two account populations that must not be summed.

Last modified

Summary

  • Environment: Internal test environment
  • Operational impact: Possible exposure across two account datasets; no confirmed password or PIN leakage
  • Financial impact: No confirmed incident cost quantified
  • Record status: Developing record. Reviewed November 18, 2026; updated as evidence emerges.

What happened

Rakuten Securities detected a possible intrusion into its test environment on November 16, 2026. Its subsequent investigation identified possible exposure associated with unauthorized access on November 11. [1]

Impact

One potentially affected dataset covers up to 4.47 million accounts. It includes customer codes and login IDs, names and kana names, birth dates, contact details, employer information, withdrawal-bank details, self-reported income and financial assets, product holdings and last-login dates. [1]

A second population covers up to 11.25 million accounts with branch/customer codes and login IDs. The two populations are not a combined unique-person count; Rakuten Securities login IDs are distinct from Rakuten IDs. [1]

Rakuten Securities said it had not confirmed leakage of passwords, PINs or trading authentication credentials, or incident-linked unauthorized account access or trades. [1]

Timeline

  1. Potential data-exposure date identified

    The date comes from the subsequent investigation, not the initial detection.

    [1]
  2. Possible intrusion detected

    Blocking and corrective measures began.

    [1]
  3. Possible exposure disclosed

    The company described the two account populations separately.

    [1]
  4. Briefing updated

    This briefing was last reviewed and updated on November 18, 2026.

Threat Group & Attack Vector

The company confirmed unauthorized access to a test environment; the cause and technical entry method remained under investigation. [1]

Actors

  • No threat actor identity is established in the reviewed evidence.

TTPs

  • No specific MITRE ATT&CK technique is mapped for this case.

Response

Rakuten Securities blocked the access route, applied corrective measures and was notifying identified affected customers individually. [1]