Yaamlabs
Threat intel

TSMC employee data leaked through a cloud vendor

TSMC says records on about 46,000 current and former employees came from a cloud provider it uses, not its own network. Why that happens and what to do.

By Yaali. November 16, 2026, 6 min read, Threat intel, Resilience.

Cover illustration of employee records flowing from a chip plant to an exposed cloud store, with the Yaamlabs logo and the text: TSMC employee data leaked through a cloud vendor, 46,000 records

Taiwan Semiconductor Manufacturing Company (TSMC), the world's largest contract chipmaker, confirmed in mid-November 2026 that personal data on current and former employees had been posted online. The detail that matters for every other company is where the data came from: TSMC's own investigation found the leaked records matched data held in a cloud service provider's systems, and it said it has no evidence that its own systems were breached.

That makes this a different kind of incident from the breaches that dominate security reporting. No one patched a gateway too late and no one ran a payload on a TSMC server. Employee data had been handed to a third party to process, as HR data routinely is, and the third party is where it leaked. About 46,000 people are affected, and the records include national identity numbers, home addresses and bank account details, so the fallout lands on individuals even though the chipmaker's network was never touched.

Stat tiles showing about 46,000 employee records, a 6.9 GB dataset, an opening bid of 3 BTC and a first free-release deadline of 15 November 2026

How employee data ends up outside the company

Modern human resources runs on outside software. Payroll, benefits enrolment, pensions, expense handling, background checks, identity verification and employee help desks are usually bought as software as a service (SaaS), which means the vendor stores and processes the data on its own infrastructure rather than yours. To do that work the vendor needs the real fields: legal name, date of birth, national identity number, home address, bank account for salary payment, and often emergency contacts.

Each copy is a place the data can leak from, and the vendor's security is now your exposure. The common failure points are mundane: a storage bucket left open to the internet, an access rule that grants far more than the one service needs, or a set of vendor credentials stolen through an infostealer or reused from an earlier breach. None of these touches the customer's own network. The attacker reaches the processor, pulls the records, and the first sign the employer sees is a sample file on a forum.

Under data protection law the company that collected the data stays responsible for it. In the language of the General Data Protection Regulation (GDPR) and similar regimes, the employer is the data controller and the SaaS firm is the processor, and the controller owns the duty to investigate, to notify regulators and to tell affected people. A contract can push some cost and liability onto the vendor, but it cannot move the obligation to the employees whose identity numbers are now for sale. TSMC is the one notifying staff and arranging support, not the unnamed provider.

What was advertised, and what TSMC found

A seller offered the data on the dark-web forums DarkForums and BreachForums. A sample file, named tsmc.txt and holding 499 rows with 19 fields each, was posted around 8 November 2026, and screenshots of the listing spread more widely over 11 and 12 November. The 19 fields reported in the sample include names, dates of birth, job titles, nationality, national identity numbers, home addresses, personal phone numbers, email addresses, bank account details and emergency contacts.

The full set was advertised at about 6.9 gigabytes covering roughly 46,000 records, with some reports putting the count nearer 49,000. The seller ran it as an auction opening at 3 bitcoin (BTC). Outlets disagree on the dollar equivalent: BleepingComputer put 3 BTC at around 65,000 US dollars, while CyPro and KuCoin reported figures of roughly 214,000 to 220,000 US dollars. The firm number is 3 BTC; treat the dollar conversions with caution. The seller said that if no buyer appeared the data would be released free within about a week, giving a first deadline around 15 November.

Diagram tracing employee records from TSMC human resources to a third-party cloud service provider, where a weakly secured store leaks the data onto a dark-web forum, while TSMC's own network stays untouched

TSMC confirmed the posting on 12 November. It said some current and former employee data had been made available on an external website without authorization, that a preliminary comparison showed the leaked content matched data stored by a cloud service provider it works with, and that it had found no evidence its internal information technology systems or wafer manufacturing equipment were compromised. It added that the data did not involve chip production or customer information, that it was notifying affected people, and that it was working with the provider, law enforcement and outside cybersecurity firms. The provider has not been named and the method of access has not been disclosed, so do not assume which vendor or what weakness was involved.

This is a separate event from two earlier TSMC incidents sometimes confused with it: a 2023 listing by the LockBit ransomware group that traced back to a hardware supplier, Kinmax, and a 2025 insider case over alleged theft of 2-nanometre chip trade secrets. Neither is connected to this employee-data leak.

What to do

The work here sits in vendor data governance, since there is nothing of your own to patch. If you hold employee data in outside systems, run these in order.

  1. Build an inventory of every third party that holds employee personally identifiable information (PII), and record which categories each one holds. Most organisations cannot answer this from memory, and you cannot protect or notify on data you have not mapped.
  2. Set contract terms that match the sensitivity. Require encryption of the data at rest, access scoped to least privilege so each service reaches only the fields it needs, a breach-notification service level agreement (SLA) with a fixed number of hours, and a right to audit the vendor's controls.
  3. Minimise what you send. Strip fields a processor does not need for its job, mask or tokenise identity and bank numbers where the vendor only needs to match on them, and delete records on the schedule the contract sets rather than letting them accumulate.
  4. Watch for your data in the wild. Monitor the dark-web forums and paste sites where samples first appear, using your company name, employee email domains and known internal identifiers as search terms, so you learn of a leak from your own monitoring rather than from a journalist.

If you may be one of the affected people

Leaked national identity numbers, home addresses and bank account details are the raw material for identity theft, targeted phishing and financial fraud, and that risk does not expire. Place a credit freeze or fraud alert with the relevant credit bureaus so no one can open accounts in your name, and turn on your existing credit monitoring if you have it. Set transaction alerts with your bank and watch for payments you did not make. Treat any unexpected call, message or email that references your real employer, job title or address as a likely scam built from the leaked file, and never act on an urgent request to move money or confirm credentials because the caller knows those details.

The wider lesson

An organisation can suffer a serious employee-data breach without a single one of its own machines being compromised, because the data now lives in systems it does not run. That turns third-party risk management and data minimisation from paperwork into the controls that decide how bad the next incident is. The fewer processors that hold the real identity and bank fields, and the tighter the access to the ones that do, the smaller the set of places a leak can start.

If you do not yet have a map of what you expose and who holds your data, that is where attack surface management begins, and testing how an attacker would move from a leaked token to the records behind it is the core of our cloud and Kubernetes security work. For the contract terms, notification duties and evidence a regulator or assessor expects, see compliance and audit readiness. Open the chat and Yaali, our AI agent, will pass your question to the engineer who would do the work.


Sources: BleepingComputer, CyPro, KuCoin.

Read next

Back to the blog, or tell us about your system in the chat. Yaali, our AI agent, answers first and brings in an engineer.