← All playbooks
HighBreach · 2026-11-19

Rakuten Securities breach: attacker hit a test environment holding real customer data, up to 11.25 million accounts exposed

SockAnalyst · Security+ certified analyst.

What happened

On November 17, 2026, Rakuten Securities said a third party gained unauthorized access to its systems. It detected possible unauthorized access on Monday, November 16, cut off and fixed the affected part, and found that information held in a test-environment system may have been taken on November 11. Up to about 11.25 million accounts had branch/customer codes and login IDs exposed, and for up to about 4.47 million of them the data also includes name, date of birth, address, phone, email, employer, withdrawal bank account, self-reported income and financial assets, per-product holdings and last login date; closed accounts are included. Passwords and trading PINs were not confirmed leaked, and no fraudulent access or trades tied to the incident had been confirmed. Rakuten Securities told ITmedia that production data had been copied to a test server without masking to verify functions during an internal system upgrade, and that attackers exploited a vulnerability; it has not named the flaw or the attacker.

Who's affected

Current and former Rakuten Securities customers (expect targeted phishing, SMS and phone fraud using accurate personal and bank details). For defenders everywhere, the lesson is that test and staging systems holding copied production data need production-grade controls.

✅ Fix / patch

  • Customers: set up passkey (FIDO2) login, consider the self-service temporary suspension of trading and withdrawals, and treat any email, SMS or call claiming to be Rakuten Securities as suspect; the company says its emails contain no URLs and it never asks for login details by phone.
  • Defenders: inventory non-production environments for copies of production personal data; delete, mask or replace with synthetic data, and set an expiry for any approved exception.
  • Put test and staging systems behind the same access controls as production: no direct internet exposure, MFA, patching SLAs, and logging that reaches your SIEM.
  • Brokerages and banks: tune fraud rules for account-takeover attempts using leaked login IDs plus personal data, and brief help desks on social-engineering calls that quote real customer details.

🔎 Quick hunt check

Rakuten Securities has not published IOCs, the vulnerability exploited, or attacker details. Hunt your own environment for the same failure mode: (1) large outbound transfers or database exports from hosts tagged test, staging, dev or UAT; (2) internet-facing services on non-production hosts; (3) for anyone serving Japanese retail investors, inbound mail impersonating Rakuten Securities (rakuten-sec) from domains you do not expect.

MITRE ATT&CK: T1190, T1005, T1041, T1566

IOCs

No IOCs (IPs, domains or hashes) published by the sources yet.

Hunt queries

Starting points built only from published indicators. Field names vary; tune before use.

```Rakuten Securities lesson: large outbound transfers from non-production hosts, plus Rakuten Securities-themed inbound mail```
index=* earliest=-30d
((sourcetype=*firewall* OR sourcetype=*traffic* OR tag=network) OR (sourcetype=*mail* OR tag=email))
| eval h=lower(coalesce(src_host, host, src_nt_host, ""))
| eval nonprod=if(match(h,"(test|tst|stg|staging|dev|uat|qa|sandbox)"),1,0)
| eval out_bytes=tonumber(coalesce(bytes_out, sent_bytes, bytes, 0))
| eval sender=lower(coalesce(src_user, sender, from, "")), subj=coalesce(subject, "")
| eval signal=case(
    nonprod=1 AND out_bytes>0 AND NOT cidrmatch("10.0.0.0/8",dest) AND NOT cidrmatch("172.16.0.0/12",dest) AND NOT cidrmatch("192.168.0.0/16",dest), "nonprod_outbound",
    match(subj,"(?i)楽天証券|rakuten securities|rakuten-sec") AND NOT match(sender,"@(mail\.)?rakuten-sec\.co\.jp$"), "rakuten_sec_lookalike_mail",
    true(), null())
| where isnotnull(signal)
| stats sum(out_bytes) as total_out count min(_time) as first_seen max(_time) as last_seen values(dest) as dests values(subj) as subjects by signal, h, sender
| where signal!="nonprod_outbound" OR total_out > 500000000
| convert ctime(first_seen) ctime(last_seen)
| sort - total_out
// Rakuten Securities lesson: big outbound transfers from non-production hosts + Rakuten Securities-themed inbound mail
let Since = ago(30d);
union isfuzzy=true
(CommonSecurityLog | where TimeGenerated >= Since
 | where SourceHostName matches regex @"(?i)(test|tst|stg|staging|dev|uat|qa|sandbox)" and not(ipv4_is_private(DestinationIP))
 | summarize TotalOut = sum(SentBytes), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated), Dests = make_set(DestinationIP, 20) by Who = SourceHostName
 | where TotalOut > 500000000
 | extend Signal = "nonprod_outbound"),
(EmailEvents | where TimeGenerated >= Since
 | where EmailDirection == "Inbound" and Subject has_any ("楽天証券","Rakuten Securities","rakuten-sec") and not(SenderFromDomain endswith "rakuten-sec.co.jp")
 | summarize Hits = count(), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated), Subjects = make_set(Subject, 20) by Who = SenderFromDomain
 | extend Signal = "rakuten_sec_lookalike_mail")
| order by LastSeen desc

See all hunt queries →

⏱ CISA deadline

Not in CISA KEV as of Nov 22, 2026.

Sources

Related playbooks

Get the SockAnalyst Weekly Brief free, every Thursday.

One email a week with the KEV deadlines, patches and hunt queries that matter. New playbooks still post here on the site every morning.

Subscribe free

Read the free weekly pack →