Threat reportData BreachTL-2026-6107
TSMC Employee Data Breach Linked to Third-Party Cloud Service Provider (Actor 'SmithBianl' Auctions 46,000 Records)
TSMC confirmed that personal data of current and former employees was posted online after a threat actor, 'SmithBianl', auctioned a claimed 6.9GB dataset of about 46,000 employee records. TSMC says the leaked data matches data held in a cloud service provider's system services and that it has found no evidence its own systems were compromised.
Key facts
| Identifiers | TL-2026-6107 |
|---|---|
| Severity | HIGH |
| Affected products | Taiwan Semiconductor Manufacturing Company (TSMC) Current and former employee personal data held by an unnamed third-party cloud service provider |
| Attribution | SmithBianl (low confidence) |
| MITRE ATT&CK techniques | T1078.004 Valid Accounts: Cloud Accounts, T1199 Trusted Relationship, T1530 Data from Cloud Storage, T1567 Exfiltration Over Web Service, T1657 Financial Theft |
| Motivation | FINANCIAL |
| Target sectors | semi-conductors, technology, manufacturing |
| Target regions | Asia-Pacific, taiwan |
| Detection rules | 9 (1 shown free) |
| Sources | 9 cited sources |
Detection coverage
As of 2026-11-15, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-6107 across Splunk SPL, Microsoft KQL and Sigma, covering 10 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.
Free detection: TL-2026-6107 Cross-Account AssumeRole From External AWS Account (Trusted Relationship / Cloud Account Abuse)
Detects successful sts:AssumeRole calls where the calling AWS account differs from the account that owns the role. TSMC states the leaked employee data matches data held by an unnamed third-party cloud service provider (T1199 Trusted Relationship); the access path into that provider is unknown. Vendor or provider identities entering a tenant through cross-account roles (T1078.004) are the most plausible entry point to hunt for. Behavioral hunt hypothesis for TL-2026-6107, not tied to a published indicator.
- Languages: Splunk SPL, Microsoft KQL, Sigma
- ATT&CK: T1199, T1078.004
- Data sources: aws_cloudtrail, index=aws sourcetype=aws:cloudtrail, AWSCloudTrail
- Severity: high
- Confidence: medium
Splunk SPL
```Cross-account AssumeRole succeeded: caller account differs from role-owning account (T1199, T1078.004)```
index=aws sourcetype="aws:cloudtrail" eventSource="sts.amazonaws.com" eventName=AssumeRole earliest=-24h
| where isnull(errorCode) AND 'userIdentity.accountId'!=recipientAccountId
| eval caller_account='userIdentity.accountId', role_arn='requestParameters.roleArn'
| stats count AS assume_count dc(sourceIPAddress) AS src_ip_count values(sourceIPAddress) AS src_ips min(_time) AS first_seen max(_time) AS last_seen BY caller_account recipientAccountId role_arn
| eval first_seen=strftime(first_seen,"%F %T"), last_seen=strftime(last_seen,"%F %T")
| sort - assume_countMicrosoft KQL
AWSCloudTrail
| where TimeGenerated > ago(24h)
| where EventSource == "sts.amazonaws.com" and EventName == "AssumeRole"
| where isempty(ErrorCode)
| where UserIdentityAccountId != RecipientAccountId
| extend RoleArn = tostring(parse_json(RequestParameters).roleArn)
| summarize AssumeCount = count(), SourceIPs = make_set(SourceIpAddress, 20), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated) by CallerAccount = UserIdentityAccountId, RecipientAccountId, RoleArn
| order by AssumeCount descSigma
title: AWS Cross-Account AssumeRole From External Account (TL-2026-6107)
id: 6f1c2a4e-3b7d-4e0a-9a51-7d2c8e41b601
status: experimental
description: Detects successful sts:AssumeRole calls made by an external AWS account (userIdentity.type AWSAccount). Hunts third-party/provider trust abuse (T1199, T1078.004) relevant to the TSMC cloud-provider employee data exposure.
references:
- https://www.bleepingcomputer.com/news/security/tsmc-employee-data-breach-linked-to-cloud-provider/
author: Threadlinqs Team
date: 2026-11-15
tags:
- attack.initial-access
- attack.t1199
- attack.t1078.004
logsource:
product: aws
service: cloudtrail
detection:
selection:
eventSource: sts.amazonaws.com
eventName: AssumeRole
userIdentity.type: AWSAccount
filter_failed:
errorCode|exists: true
condition: selection and not filter_failed
falsepositives:
- Approved vendors, managed service providers and internal multi-account (AWS Organizations) role assumption
- CI/CD or backup tooling hosted in a separate AWS account
level: medium
Known false positives:
- Approved managed-service-provider or vendor cross-account roles
- Internal AWS Organizations multi-account automation (CI/CD, backup, security tooling)
Tuning notes: Allowlist known vendor/organization account IDs (lookup or watchlist) and alert only on unknown caller accounts. Prioritise roles that grant S3, RDS, or HR/payroll data access. Requires the CloudTrail management-events feed in the target account.
- TL-2026-6107 Guest / Vendor Identity Sign-In To Azure Management Tooling From New IP · unlock with TL Creds
- TL-2026-6107 Azure Storage Account Key Listing Burst By Single Caller (Cloud Storage Access Precursor) · unlock with TL Creds
- TL-2026-6107 Corporate Host Contact With DarkForums / BreachForums Leak Venues · unlock with TL Creds
- TL-2026-6107 AWS Console Login By IAM User Without MFA · unlock with TL Creds
- TL-2026-6107 AWS IAM Persistence: New Keys, Users Or Trust Policy Changes By Assumed / External Principal · unlock with TL Creds
- TL-2026-6107 AWS Data Transfer To External Account: Snapshot/AMI Sharing Or Bucket Replication · unlock with TL Creds
- TL-2026-6107 AWS S3 Bulk Object Retrieval By Single Identity (Data from Cloud Storage) · unlock with TL Creds
- TL-2026-6107 Large HTTP Upload To File-Sharing / Anonymous Hosting Services (Exfiltration Over Web Service) · unlock with TL Creds
Indicators of compromise
As of 2026-11-15, Threadlinqs Intelligence tracks 10 indicators of compromise for TL-2026-6107.
Sample indicators (2 of 10)
- URL:
hxxp://www[.]sec[.]gov/Archives/edgar/data/1046179/000104617926000800/a20261112statementregardin.htm - URL:
hxxps://www[.]bleepingcomputer[.]com/news/security/tsmc-employee-data-breach-linked-to-cloud-provider/
Defanged, TLP:CLEAR. Full set of 10 indicators: unlock with TL Creds.
Technical analysis
On 2026-11-08 a forum actor using the alias 'SmithBianl' posted a 499-row text file (reported as 'tsmc.txt') as a sample of data allegedly stolen from TSMC, and offered the full dataset - claimed as 6.9GB and about 46,000 employee records - for auction with a starting bid of 3 BTC. The actor reportedly set a one-week deadline, after which unsold data would be leaked for free (first deadline 2026-11-15). Secondary reporting names DarkForums and BreachForums as the venues; BleepingComputer refers only to an unnamed 'hacker forum' and credits KELA for the forum screenshot, and AMBCrypto refers only to 'an underground forum'.
TSMC filed a Form 6-K with the SEC dated 2026-11-12 (signed by CFO Wendell Huang, 'Statement Regarding the Unauthorized Access of Employee Personal Data'). It states that some current and former employee data was made available on an external website without authorization, that the data was verified to match data stored in the system services of a cloud service provider, that it is unrelated to TSMC operations or customer data, and that 'Currently, we have found no evidence that TSMC's systems have been compromised.' TSMC is notifying and supporting affected staff and has engaged the cloud provider, relevant investigative bodies and a third-party cybersecurity firm. The cloud provider has not been named. A TSMC spokesperson declined to tell BleepingComputer whether it had engaged with the actor or would pay.
Claimed data fields vary by outlet: national ID numbers, home addresses, contact details (phone, email) and banking information (BleepingComputer); names, birth dates, job titles, nationalities, emergency contact details and bank account numbers (other outlets). All volume, record-count and field claims originate from the seller and are unverified by TSMC; TSMC has only confirmed that the leaked data matches data held by the cloud provider. Source discrepancies: record count is reported as ~46,000 by most outlets (one headline says 49,000); the 3 BTC price is reported as ~$65,000 by BleepingComputer but ~$215-220K by other outlets using a higher BTC price; AMBCrypto states the seller is seeking a buyer rather than demanding a ransom from TSMC.
No CVE, malware family, or technical indicators (IPs, domains, hashes, wallet addresses) have been published, so no BeaconBeagle network correlation was possible. The initial access vector into the cloud provider environment is unknown. This is assessed as a third-party / supply-chain data exposure with a financially motivated seller. Defenders should treat affected employees as at elevated risk of identity theft, targeted phishing/vishing and fraud, and organizations that use the same unnamed provider should review access and data-exposure posture.
MITRE ATT&CK techniques by tactic:
Initial Access
T1078.004 Valid Accounts: Cloud Accounts; T1199 Trusted Relationship
Collection
Exfiltration
T1567 Exfiltration Over Web Service
Impact
Remediation
Immediate actions
- Notify affected current and former employees and offer identity-theft and credit monitoring support
- Warn staff about targeted phishing, vishing and smishing that abuses leaked personal details
- Work with the cloud service provider to identify the access path, revoke credentials/tokens and preserve logs
- Monitor DarkForums, BreachForums and other leak venues for publication of the dataset
Workarounds
- Employees should be alerted to freeze credit where available, change banking credentials if exposed, and treat unsolicited contact referencing personal data as suspicious
Longer-term hardening
- Perform third-party/vendor risk review of cloud providers holding employee PII, including data minimization and retention limits
- Enforce MFA, least privilege and logging on vendor-managed cloud tenants and storage
- Encrypt sensitive HR fields (national ID, banking) at rest with customer-managed keys
Affected and fixed versions
- Taiwan Semiconductor Manufacturing Company (TSMC) — Current and former employee personal data held by an unnamed third-party cloud service provider
Timeline
- SmithBianl offers a claimed 6.9GB / ~46,000-record employee dataset for auction with a 3 BTC starting bid and a one-week deadline before a free leak; other outlets name DarkForums and BreachForums.
- Actor 'SmithBianl' posts a 499-row text file (reported as locked-ioc-3) on a hacker forum as a sample of allegedly stolen TSMC employee data.
- Wccftech, Benzinga, PC Gamer, AMBCrypto, Cryptopolitan and other outlets report the incident; TSMC says it is notifying affected staff and working with the cloud provider, investigative bodies and a third-party cybersecurity firm.
- TSMC files a Form 6-K (signed by CFO Wendell Huang) stating employee data was posted externally without authorization, matches data held by a cloud service provider, and that it has no evidence its own systems were compromised.
- TSMC declines to tell BleepingComputer whether it engaged with the actor or plans to pay; the cloud provider remains unnamed.
- First deadline set by the actor for releasing the data for free if unsold; BleepingComputer publishes its report citing KELA's forum screenshot.
Sources cited
- TSMC SEC Form 6-K: Statement Regarding the Unauthorized Access of Employee Personal Data sec.gov · Advisory · 2026-11-12
- KELA Cyber (source of forum screenshot cited by BleepingComputer) kelacyber.com · Research · 2026-11-08
- TSMC employee data breach linked to cloud provider BleepingComputer · News · 2026-11-15
- Taiwan Chip Giant TSMC Acknowledges Hack Of Reportedly 49,000 Employee Files (Wccftech) wccftech.com · News · 2026-11-12
- TSMC Confirms Employee Data Leak Through Cloud Provider, Hackers Reportedly Demand 3 Bitcoins (Benzinga) benzinga.com · News · 2026-11-12
- Chipmaking giant TSMC discovers major employee data leak (PC Gamer) pcgamer.com · News · 2026-11-12
- TSMC confirms data breach as hacker demands Bitcoin worth $215K (AMBCrypto) ambcrypto.com · News · 2026-11-12
- TSMC blames cloud vendor as hackers sell staff data for 3 BTC (Cryptopolitan) cryptopolitan.com · News · 2026-11-12
- TSMC faces $70 million LockBit ransom demand following hardware supplier breach (ITPro) - 2023 prior third-party incident for context itpro.com · News · 2023-06-30
Drafted by the Threadlinqs research pipeline from 9 sources; published ; last updated —.