Daishin Securities Confirms Data Breach Affecting 38,490 Customers

Daishin Securities says personal and credit information for 38,490 customers was compromised. Here is what was reported, what remains unknown, and how to verify breach-related messages safely.

Reader ratingRate this article

Loading reader rating…

Privacy-conscious voting uses a signed random browser identifier and a short-lived network hash; the rating tables contain no raw IP-address column.

Reader ratings require JavaScript; the article remains fully readable without it.

Glowing blue shield struck by red data fragments in front of customer-record cards and an open vault.
AI-generated editorial illustration of customer records behind a fractured digital shield beside an open vault. Not official Daishin Securities imagery.

Daishin Securities Confirms Data Breach Affecting 38,490 Customers12

Daishin Securities says personal and credit information belonging to 38,490 customers was compromised.12 The two opened reports carry the same affected count, but both ultimately attribute the disclosure to the brokerage rather than an independently published forensic report.12

CUSTOMER SAFETY • Reporting cutoff: October 28, 2026, 2:26 a.m. EDT123

The bottom line

The reported affected group is Daishin Securities customers; the reviewed sources do not identify a United States or Florida cohort.12 For other readers, the practical risk is convincing financial impersonation that uses real identity or account context. Verify any breach message through an official website, app or main customer-service number rather than the contact details in the message.3

Verified facts

Affected customers38,490 customers, according to Daishin Securities.12
Reported dataEight categories of personal and credit information.1
Detection and confirmationAbnormal access was detected October 17; Daishin says it confirmed the leak October 26 after a ten-day review.1

What happened

Daishin says it detected unauthorized access on a server linked to non-face-to-face account opening for discretionary investment accounts.1 The company says it blocked attack and bypass IP addresses, reported the incident to regulators and investigated with the Korea Financial Security Institute.1

The company says its review covered more than 60,000 signals disguised as normal service traffic.1 That figure describes reviewed signals, not a customer or stolen-record count.

What information was reported exposed

The reported categories were names, email addresses, physical addresses, telecommunications IDs, bank names, encrypted deposit and withdrawal account numbers, encrypted Daishin comprehensive account numbers and encrypted mobile phone numbers.1 Yonhap separately names names, email addresses and mobile phone numbers while carrying the same 38,490-customer figure.2

What the company says about impact

Daishin says it had found no evidence of secondary customer harm so far and no unauthorized access to core business systems.1 Those are company findings relayed by Herald Business, not independently audited conclusions.

Daishin says it will notify affected customers individually about the specific exposed fields and take prompt action if harm is confirmed.1

What readers should do

  1. Verify through an official channel. The South Korean Financial Services Commission advises checking whether information was exposed, and which fields were involved, through the financial company’s official website, app or main customer-service number.3
  2. Do not disclose authentication secrets or transfer money because of an unexpected message. The FSC says financial authorities and financial companies do not request passwords or authentication codes by phone or text, and do not request transfers for compensation or account protection.3
  3. Distrust tailored outreach even when it knows real details. The FSC warns that exposed personal information can be combined into convincing loan, compensation and account-protection impersonation.3

What remains unknown

The reviewed sources do not identify the initial access vector, a vulnerability, malware, a threat actor, the exact access duration or whether every affected customer had the same fields exposed.12 They also do not establish whether the encrypted fields can be decrypted or correlated with other datasets.12

No company-hosted public advisory or regulator incident record was located by the reporting cutoff. The detailed account is therefore presented as Daishin’s statement carried by Herald Business, with Yonhap corroborating the count and core categories.12

Sources

  1. Daishin Securities apologizes for data breach affecting 38,000 customers — Herald Business, October 28, 2026.
  2. Personal data of some 38,000 customers at Daishin Securities leaked — Yonhap News Agency, October 28, 2026.
  3. FSC consumer alert on phishing and smishing after financial-sector data leaks — Financial Services Commission, October 6, 2026.

Source cutoff: This article reflects the three sources checked through October 28, 2026, 2:26 a.m. EDT; later changes require a new source review before publication.123

Browse Articles

Latest Articles