<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Visual Studio Code Marketplace — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/visual-studio-code-marketplace/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Thu, 21 May 2026 06:54:47 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/visual-studio-code-marketplace/feed.xml" rel="self" type="application/rss+xml"/><item><title>GitHub Breach Linked to TanStack npm Supply Chain Attack via Malicious VS Code Extension</title><link>https://feed.craftedsignal.io/briefs/2026-05-github-repo-breach/</link><pubDate>Thu, 21 May 2026 06:54:47 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-github-repo-breach/</guid><description>GitHub experienced a breach affecting 3,800 internal repositories due to a supply chain attack targeting TanStack npm packages; the attacker compromised an employee's machine via a malicious version of the Nx Console VS Code extension and gained access to internal GitHub repositories by stealing credentials and secrets.</description><content:encoded><![CDATA[<p>On May 21, 2026, GitHub revealed that a breach affecting 3,800 internal repositories occurred due to a supply chain attack. This attack, attributed to the TeamPCP threat group, originated with the compromise of TanStack npm packages and quickly spread to other projects including UiPath, Guardrails AI, and OpenSearch. The initial compromise involved a malicious version of the Nx Console Visual Studio Code (VS Code) extension. The attacker gained access by compromising a developer&rsquo;s machine, stealing credentials, and exploiting the GitHub CLI (gh) to run workflows on the GitHub repository as a contributor. While GitHub has secured the compromised device and rotated critical secrets, the incident highlights the significant risks associated with supply chain attacks targeting developer tools and code repositories.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>The attacker compromises the TanStack npm packages in a supply chain attack.</li>
<li>A developer installs the malicious Nx Console (version 18.95.0) VS Code extension from the Visual Studio Marketplace or OpenVSX.</li>
<li>The malicious extension executes a payload designed to steal credentials and secrets for platforms like npm, AWS, Kubernetes, GitHub, and GCP/Docker.</li>
<li>The compromised developer&rsquo;s GitHub credentials are leaked through the GitHub CLI (gh).</li>
<li>The attacker uses the stolen GitHub credentials to authenticate and run workflows on the GitHub repository.</li>
<li>The attacker gains unauthorized access to approximately 3,800 of GitHub&rsquo;s internal repositories.</li>
<li>The attacker exfiltrates source code and other sensitive data from the breached repositories.</li>
<li>TeamPCP attempts to sell the stolen data for at least $50,000 on the Breached forum.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>The successful exploitation resulted in the unauthorized access to approximately 3,800 of GitHub&rsquo;s internal repositories. The attacker, TeamPCP, is attempting to sell the stolen data, including source code, for at least $50,000. This breach could lead to the exposure of sensitive internal code, security vulnerabilities, and proprietary information, potentially impacting GitHub&rsquo;s competitive advantage and the security of its platform. The incident underscores the increasing risk of supply chain attacks targeting developer tools and the need for robust security measures to protect against compromised dependencies.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Monitor VS Code extension installations and deployments for suspicious activity, focusing on extensions related to Nx Console or TanStack, using a process creation rule (see &ldquo;Detect Suspicious VS Code Extension Execution&rdquo;).</li>
<li>Implement multi-factor authentication (MFA) for all developer accounts and regularly rotate credentials for critical services such as npm, AWS, Kubernetes, GitHub, and GCP/Docker.</li>
<li>Deploy the Sigma rule &ldquo;Detect Credential Theft via Malicious VS Code Extension&rdquo; to identify attempts to steal credentials using known malicious file names or file paths.</li>
<li>Monitor network connections originating from VS Code extensions to detect unauthorized data exfiltration or communication with suspicious domains or IP addresses.</li>
<li>Review and harden CI/CD pipelines to prevent the use of stolen credentials, focusing on securing access to sensitive resources and monitoring for unauthorized workflow executions.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">threat</category><category>supply-chain</category><category>vscode</category><category>npm</category><category>github</category><category>credential-theft</category></item></channel></rss>