NEWS

TSMC Confirms Employee Data Leak Tied to a Cloud Service Provider

TSMC says leaked employee data matches records at a cloud provider it uses. An actor auctioned 6.9GB from 3 BTC; TSMC found no breach of its own systems.

Dylan H.

News Desk

November 15, 2026
2 min read
TSMC Confirms Employee Data Leak Tied to a Cloud Service Provider

Summary

Taiwan Semiconductor Manufacturing Company (TSMC) has confirmed that personal data on its employees was made available on an external website without authorization. TSMC says the leaked data matches data stored in the system services of a cloud service provider it uses, which points to a third-party breach rather than a compromise of TSMC's own network.

What was leaked

A threat actor using the alias "SmithBianl" claims to hold a 6.9GB dataset covering about 46,000 current and former employees. According to the actor's post, the data includes national ID numbers, addresses, contact details and banking information. These claims are unverified.

ItemDetail
Claimed size6.9GB, about 46,000 employee records
Sample499 rows posted on a hacker forum on November 8
AuctionStarting at 3 BTC (about $65,000)
DeadlineFree leak if no buyer by November 15

TSMC's response

In an SEC filing, TSMC said it found no evidence that its own systems were compromised and that the incident does not affect operations or customers. It is notifying affected employees, offering support, and has engaged a third-party cybersecurity firm. TSMC declined to say whether it had contacted the actor or planned to pay.

Why it matters

The incident is another example of third-party and cloud-provider risk: a large company with strong perimeter controls can still leak staff data through a vendor. National ID and banking details make affected employees targets for identity fraud and tailored phishing.

  1. Affected employees should watch bank accounts and treat unsolicited calls or messages about their ID or pay details with suspicion.
  2. Organizations should inventory which vendors hold HR and payroll data and review the access keys and storage settings on those platforms.
  3. Require vendors to notify you promptly of incidents, and rotate credentials shared with them after any report.

Sources