CVE Index中文
L4 · Septic Tank BlewMirae Asset Securities · Brokerage · Data breachmirae-asset-securities-data

Mirae Asset Securities confirms customer account numbers and workforce data leaked

Mirae Asset Securities confirmed the exposure of account numbers for about 3,800 customers and personal data for about 35,255 current and former staff and contractors. The broker shut down the affected mobile-web login service and isolated the groupware server. Both entry paths remain under investigation.

Disclosed
Nov 7, 2026
Public disclosure date
Severity
Septic Tank Blew
No CVE: a breach, not a bug
Splash zone
About 3,800 customers and 35,255 staff, former staff and contractors of South Korea’s Mirae Asset Securities.
Mirae Asset Securities · Brokerage · Data breach
In the wild
Yes
The broker confirms external attacks and data leakage from two services.

What happened

On November 7, Mirae Asset Securities disclosed intrusions affecting two services on consecutive days. Its customer notice says an external party accessed the mobile website’s phone-verification login flow on November 4. About 3,800 customers’ brokerage account numbers leaked. The broker says account-holder names and other customer fields were outside that exposure. It suspended the login service after discovering the leak and kept it disconnected from external access while investigating.

The November 5 attack affected the broker’s mi-global groupware. The workforce notice counts about 35,255 people, including former employees and contractors. The exposed data consisted mainly of names and employee IDs, with email addresses, mobile numbers and passwords described as encrypted exposed for some people. The fields vary by person. The notice gives no password protection scheme or evidence that the exposed passwords were recovered in usable form. The broker disconnected the affected server, kept groupware and related mobile services isolated from external access, and expanded checks to other internet-accessible internal systems.

The two notices count different groups, and the company does not give a deduplicated total. They provide no technical entry mechanism, shared-attacker attribution, confirmed financial losses or reopening time for the affected login and groupware services.

Crime-scene timeline

  1. Nov 4, 2026

    External access targets the mobile-web login service

    The broker reports abnormal access to its phone-verification login flow and says the only exposed customer field was the brokerage account number.

  2. Nov 5, 2026

    External attack targets the mi-global groupware

    The broker confirms workforce data leaked and says it disconnected the affected server after discovering the incident.

  3. Nov 7, 2026

    The broker publishes separate customer and workforce notices

    The notices identify the affected groups and data fields, describe containment and give reporting instructions.

Who said what

We list each claim and who made it. Primary sources (the vendor, the researcher, the registry) are marked. Where reports disagree, we grade by the worst credible case.