---
title: "Rakuten Securities test-environment intrusion"
description: "Rakuten Securities reported possible customer-data exposure from a test environment, with two account populations that must not be summed."
incident_type: "Cybersecurity incident"
status: "active"
last_modified: "2026-11-18"
canonical_url: "https://www.ally.security/incidents/rakuten-securities-test-environment-intrusion-2026"
markdown_url: "https://www.ally.security/incidents/rakuten-securities-test-environment-intrusion-2026.md"
stix_url: "https://www.ally.security/incidents/rakuten-securities-test-environment-intrusion-2026/stix.json"
---

# 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 Nov 18, 2026 · 1 source

## 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

## What happened

[Rakuten Securities](https://www.rakuten-sec.co.jp/) 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](#source-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](#source-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](#source-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](#source-1)

## Timeline

### November 11, 2026 — Potential data-exposure date identified

The date comes from the subsequent investigation, not the initial detection. [1](#source-1)

### November 16, 2026 — Possible intrusion detected

Blocking and corrective measures began. [1](#source-1)

### November 17, 2026 — Possible exposure disclosed

The company described the two account populations separately. [1](#source-1)

### November 18, 2026 — 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](#source-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](#source-1)

## Assets

[Download the case-scoped STIX 2.1 bundle](<https://www.ally.security/incidents/rakuten-securities-test-environment-intrusion-2026/stix.json>)

## Sources

Primary source records used to research this incident.

<a id="source-1"></a>

### Unauthorized access to a test environment and possible information leakage

official · Rakuten Securities, Inc. · Nov 17, 2026

<https://www.rakuten-sec.co.jp/web/company/newsrelease/pdf/press2026111702.pdf>

<details>
<summary>Evidence ledger</summary>

Review the supporting structured claims.

1. **Occurred At · 100% confidence · current**  
   Potential data-exposure date identified: 2026-11-11
2. **Resulted In · 100% confidence · current**  
   Rakuten Securities test-environment intrusion: A second population covers up to 11.25 million accounts with branch/customer codes and login IDs.
3. **Resulted In · 100% confidence · current**  
   Rakuten Securities test-environment intrusion: Possible intrusion detected
4. **Resulted In · 100% confidence · current**  
   Rakuten Securities test-environment intrusion: The two populations are not a combined unique-person count; Rakuten Securities login IDs are distinct from Rakuten IDs.
5. **Resulted In · 100% confidence · current**  
   Rakuten Securities test-environment intrusion: Rakuten Securities said it had not confirmed leakage of passwords, PINs or trading authentication credentials, or incident-linked unauthorized account access or trades.
6. **Resulted In · 100% confidence · current**  
   Rakuten Securities test-environment intrusion: Its subsequent investigation identified possible exposure associated with unauthorized access on November 11.
7. **Resulted In · 100% confidence · current**  
   Rakuten Securities test-environment intrusion: Rakuten Securities detected a possible intrusion into its test environment on November 16, 2026.
8. **Resulted In · 100% confidence · current**  
   Rakuten Securities test-environment intrusion: Rakuten Securities blocked the access route, applied corrective measures and was notifying identified affected customers individually.
9. **Resulted In · 100% confidence · current**  
   Rakuten Securities test-environment intrusion: Potential data-exposure date identified
10. **Affected Organization · 100% confidence · current**  
   Rakuten Securities test-environment intrusion: Rakuten Securities, Inc.
11. **Resulted In · 100% confidence · current**  
   Possible exposure disclosed: The company described the two account populations separately.
12. **Resulted In · 100% confidence · current**  
   Rakuten Securities test-environment intrusion: The company confirmed unauthorized access to a test environment; the cause and technical entry method remained under investigation.
13. **Resulted In · 100% confidence · current**  
   Rakuten Securities test-environment intrusion: 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.
14. **Resulted In · 100% confidence · current**  
   Possible intrusion detected: Blocking and corrective measures began.
15. **Occurred At · 100% confidence · current**  
   Possible intrusion detected: 2026-11-16
16. **Resulted In · 100% confidence · current**  
   Potential data-exposure date identified: The date comes from the subsequent investigation, not the initial detection.
17. **Resulted In · 100% confidence · current**  
   Rakuten Securities test-environment intrusion: Possible exposure disclosed
18. **Occurred At · 100% confidence · current**  
   Possible exposure disclosed: 2026-11-17
19. **Resulted In · 100% confidence · current**  
   Rakuten Securities test-environment intrusion: One potentially affected dataset covers up to 4.47 million accounts.

</details>
