--- title: "TSMC, Nvidia, Microsoft on 12 Nov: Not One Campaign" url: https://playciso.com/blog/tsmc-nvidia-microsoft-12-november-2026-not-one-campaign updated: 2026-11-13 section: Blog publisher: PlayCISO --- # TSMC, Nvidia, Microsoft on 12 Nov: Not One Campaign > TSMC employee data, Nvidia's CEO resignation and the Microsoft 365 outage all hit the news on 12 Nov 2026. We checked whether anything links them. Source: https://playciso.com/blog/tsmc-nvidia-microsoft-12-november-2026-not-one-campaign · Published: 2026-11-13 · Publisher: PlayCISO (https://playciso.com) Primary source: https://cybersecuritynews.com/tsmc-data-breach/ --- A viral post says TSMC "was hacked along with Microsoft on the same day Jensen Huang was fired" and asks whether a foreign actor is behind all three. **The three events are real. They are also three different kinds of event, and no source links them.** TSMC says personal data of some employees appeared online through an outside cloud provider, Nvidia says its CEO resigned, and Microsoft says its 12 to 13 November outage came from its own servers and network, with no indication of malicious activity. Only the date overlaps. **Who this is for:** security leaders asked "is this coordinated?" by a board member who saw the post, and anyone who runs a vendor-risk or communications function. *Independent analysis. PlayCISO is not affiliated with any company named. Facts as of 13 November 2026. We read Nvidia's announcement, NBC News and Cybersecurity News; we could not open TSMC's own notice, so TSMC's position is as reported.* Confirmed vs not yet known **Confirmed:** TSMC's disclosure on 12 November of an exposure of employee data linked to an outside cloud provider (per Cybersecurity News's account of TSMC's statement); Nvidia's announcement on 12 November that Jensen Huang resigned with immediate effect and Colette Kress is interim CEO (Nvidia's release); Microsoft's statement that it is not aware of malicious activity behind its outage. **Claimed or unverified:** the 46,000-record, 3-bitcoin offer on criminal forums; what the records contain; the reasons behind Huang's resignation (media reports of unverified allegations); any coordinated foreign campaign. **Not published:** how many TSMC staff are affected, which data fields, the vendor's name and how the data got out; Nvidia's stated reason for the departure. ## TSMC: a third-party exposure, not a confirmed breach of its own systems On 12 November TSMC said personal data of some current and former employees appeared online without permission. According to Cybersecurity News, which paraphrases TSMC's statement, the data matched records held by an outside cloud provider and TSMC found no evidence its own systems were compromised. TSMC is informing affected staff, working with the vendor, and investigating with authorities and an outside cybersecurity firm. It has not given a number, the data fields or the vendor's name. Anonymous sellers on criminal forums reportedly claim about **46,000 records for 3 bitcoin** (attributed to Taiwan News, which we could not open); TSMC has not confirmed that, and the sellers' descriptions of the contents are unverified. This is a new incident. TSMC's 2023 disclosure of an attack on a supplier is a different event. ## Nvidia: a resignation, not a firing Nvidia's announcement, filed with the SEC on 12 November, says Jensen Huang "has resigned as President, Chief Executive Officer, and a member of the Board, effective immediately". CFO Colette Kress is interim CEO and the board is searching for a permanent one. The release gives no reason and does not say he was fired. NBC News reports the resignation followed press reports about his personal conduct, first reported by other outlets citing unnamed people. NBC says it has not independently verified them, Nvidia did not comment, and a government named in one report denies it. We are not repeating unverified personal allegations here. This is a corporate-governance event, not a cyber incident. ## Microsoft: servers and network, no sign of an attack Microsoft's outage began at about 16:17 UTC on 12 November. Microsoft says the load came from servers becoming unavailable, not from more traffic, and that a recent network configuration change correlates with the start of impact. It says it is not aware of any malicious activity and will publish a Post-Incident Report. Our [Microsoft 365 outage article](/blog/microsoft-365-outage-november-2026) has the full timeline and checks the other claims going around, including the ConnectWise and ARTEX link and the Outlook zero-day theory. ## Why "coordinated" does not follow - Different causes. A vendor-held data exposure, an executive departure and a service outage have nothing in common that a single campaign would explain. - Different victims and methods. TSMC's data sat with an outside cloud provider; Microsoft's failure was inside Microsoft's service; Nvidia's was a board announcement. - No attribution. No government, vendor or researcher we found attributes any of them to a foreign actor. The Grok-style summaries going round say the same: no public evidence of a link. - Timing is weak evidence. Dozens of incidents are disclosed every week, and many land on the same day. Our [October roundup](/blog/october-2026-hacks-roundup-whats-confirmed) shows how a list of unrelated incidents reads like one campaign. ## What security leaders should do this week - Answer the board in one line: three separate events, no evidence of coordination, and what each means for us. - Ask your vendors the TSMC question: which of our people's records do you hold, where, and who else can reach them. Use our [third-party breach response checklist](/tools/third-party-breach-response-checklist) and [vendor risk assessment](/tools/vendor-risk). - Warn staff about phishing that uses leaked employee details and the Microsoft outage as a pretext. - Know your notification clock if a vendor tells you your data was exposed: our [breach notification clock calculator](/tools/breach-notification-clock-calculator) turns a discovery time into deadlines. - Check how much rides on one provider. The [SaaS concentration risk scorer](/tools/saas-concentration-risk-scorer) shows your single points of failure. - Verify before you share. Open the company's own statement before reposting a "coordinated attack" thread. ## FAQ ### Was TSMC hacked on 12 November 2026? TSMC says personal data of some current and former employees appeared online without permission, that it matched records held by an outside cloud provider, and that it found no evidence its own systems were compromised. It is informing affected staff, working with the vendor and investigating with authorities and an outside cybersecurity firm. It has not published a count, the data fields or the vendor's name. So this is a reported data exposure at a third party, not a confirmed breach of TSMC's own systems. ### How many TSMC records were stolen? TSMC has not said. Anonymous sellers on criminal forums reportedly claim about 46,000 records for 3 bitcoin, a claim attributed to Taiwan News by Cybersecurity News that we could not open. TSMC has not confirmed the figure, and sellers' claims about what the records contain are unverified. ### Was Jensen Huang fired? Nvidia's own announcement says he resigned: Jensen Huang "has resigned as President, Chief Executive Officer, and a member of the Board, effective immediately", and CFO Colette Kress is interim CEO while the board searches for a permanent one. The release gives no reason. NBC News reports the resignation followed press reports about his personal conduct, which NBC says it has not independently verified; Nvidia did not comment. ### Are the TSMC leak, the Nvidia resignation and the Microsoft outage connected? No source links them. They are a data exposure at a cloud provider, a leadership departure and a service outage, with different causes, and Microsoft says it is not aware of any malicious activity behind its outage. All three landing on 12 November is a coincidence of timing; there is no public evidence of a coordinated campaign by any foreign actor. ### What should companies do about a third-party data exposure like TSMC's? Ask the vendor which of your records it holds and how they were exposed, assume the data is public, notify under the rules that apply to you, warn affected people about phishing and identity fraud, and review what you share with vendors. Our third-party breach response checklist walks through the questions. ## Sources - [Nvidia announcement of CEO transition (press release, SEC EDGAR)](https://www.sec.gov/Archives/edgar/data/0001045810/000104581026000082/nvidiaannouncesceotransiti.htm) (12 Nov; read; the 8-K cover page was not seen) - [NBC News: Nvidia CEO Jensen Huang resigns](https://www.nbcnews.com/tech/tech-news/nvidia-ceo-jensen-huang-resigns-reports-extramarital-relationships-rcna608402) (12 Nov; read; NBC did not verify the underlying reports) - [Cybersecurity News: TSMC data breach](https://cybersecuritynews.com/tsmc-data-breach/) (13 Nov; read; paraphrases TSMC; TSMC's own notice and the Taiwan News report were not opened) - [PlayCISO: Microsoft 365 outage, what is confirmed](/blog/microsoft-365-outage-november-2026) (sources for Microsoft's statements are listed there) **Share:** #TSMC #Nvidia #Microsoft365 #Cybersecurity #Infosec #ThirdPartyRisk #FactCheck #DataBreach *This article is general information, not legal or security advice.*