TeamPCP Supply Chain Campaign: Activity Through 2026-06-07, (Mon, Jun 8th)
The TeamPCP supply chain campaign involves sophisticated attacks leveraging compromised build pipelines to distribute malicious code, including credential-stealing worms. Recent developments include formal U. S. government recognition with CISA adding key vulnerabilities to its Known Exploited Vulnerabilities catalog and issuing advisories. The campaign's open-sourced Mini Shai-Hulud framework has enabled widespread copycat attacks, notably compromising numerous Red Hat npm packages via a compromised employee GitHub account. Attackers use advanced install-time techniques, such as weaponizing binding. gyp files, to evade detection. Despite valid signed provenance on malicious packages, the build pipelines themselves were subverted, undermining trust in provenance attestations. Mitigation deadlines set by CISA are in place, and defenders are urged to rotate secrets, review logs, and implement enhanced detection strategies. The campaign currently shows medium severity with no active extortion activity reported.
AI Analysis
Technical Summary
The TeamPCP supply chain campaign, tracked by SANS ISC and formally acknowledged by CISA, exploits subverted build pipelines to distribute malicious artifacts, including the Mini Shai-Hulud credential-stealing worm. Key vulnerabilities (CVE-2026-45321 and CVE-2026-48027) were added to CISA's KEV catalog with a remediation deadline of 2026-06-10. The campaign's open-sourced framework has led to copycat attacks compromising at least 32 Red Hat npm packages (Miasma wave) and a follow-on Phantom Gyp wave affecting 57 additional packages. Attackers used a compromised Red Hat employee GitHub account to inject malicious GitHub Actions workflows, resulting in valid SLSA provenance attestations despite the malicious payload. Phantom Gyp introduced install-time evasion by abusing binding.gyp and node-gyp hooks, bypassing monitors focused on package.json scripts. Attribution is ambiguous due to the public availability of the Mini Shai-Hulud framework. The campaign's monetization channels remain dormant, focusing currently on ecosystem-scale worming rather than targeted extortion.
Potential Impact
The campaign enables attackers to distribute malicious code through trusted supply chain components, leading to credential theft and potential further compromise of cloud and CI/CD environments. The subversion of build pipelines allows attackers to produce validly signed malicious artifacts, undermining trust in provenance attestations. The compromise of widely used npm packages affects thousands of users and organizations relying on these packages, increasing the risk of widespread credential exposure and unauthorized access. The use of advanced install-time evasion techniques complicates detection and mitigation efforts. Although no active extortion or ransomware activity is currently observed, the campaign poses a significant medium-level threat to software supply chain integrity and cloud security.
Mitigation Recommendations
A fix is available as per CISA advisories with a remediation deadline of 2026-06-10 for CVE-2026-45321 and CVE-2026-48027. Defenders should confirm removal of the compromised Nx Console v18.95.0 and remediation of TanStack-related exposures. Rotate all CI/CD-accessible secrets and cloud credentials and review CI/CD logs and cloud audit trails as recommended by CISA. Inventory and pin affected npm packages (@redhat-cloud-services, @vapi-ai/server-sdk, and others) to known-good versions rebuilt from trusted sources. Enhance detection to monitor install-time execution beyond package.json scripts, including binding.gyp and node-gyp hooks, and consider disabling install scripts in CI environments where feasible. Do not rely solely on SLSA provenance attestations; implement build environment integrity controls and behavioral monitoring. Enforce two-factor authentication on registry maintainer accounts, narrowly scope publish tokens, and alert on anomalous workflow changes in source repositories. Monitor for further advisories and updates from vendors and government agencies.
TeamPCP Supply Chain Campaign: Activity Through 2026-06-07, (Mon, Jun 8th)
Description
The TeamPCP supply chain campaign involves sophisticated attacks leveraging compromised build pipelines to distribute malicious code, including credential-stealing worms. Recent developments include formal U. S. government recognition with CISA adding key vulnerabilities to its Known Exploited Vulnerabilities catalog and issuing advisories. The campaign's open-sourced Mini Shai-Hulud framework has enabled widespread copycat attacks, notably compromising numerous Red Hat npm packages via a compromised employee GitHub account. Attackers use advanced install-time techniques, such as weaponizing binding. gyp files, to evade detection. Despite valid signed provenance on malicious packages, the build pipelines themselves were subverted, undermining trust in provenance attestations. Mitigation deadlines set by CISA are in place, and defenders are urged to rotate secrets, review logs, and implement enhanced detection strategies. The campaign currently shows medium severity with no active extortion activity reported.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The TeamPCP supply chain campaign, tracked by SANS ISC and formally acknowledged by CISA, exploits subverted build pipelines to distribute malicious artifacts, including the Mini Shai-Hulud credential-stealing worm. Key vulnerabilities (CVE-2026-45321 and CVE-2026-48027) were added to CISA's KEV catalog with a remediation deadline of 2026-06-10. The campaign's open-sourced framework has led to copycat attacks compromising at least 32 Red Hat npm packages (Miasma wave) and a follow-on Phantom Gyp wave affecting 57 additional packages. Attackers used a compromised Red Hat employee GitHub account to inject malicious GitHub Actions workflows, resulting in valid SLSA provenance attestations despite the malicious payload. Phantom Gyp introduced install-time evasion by abusing binding.gyp and node-gyp hooks, bypassing monitors focused on package.json scripts. Attribution is ambiguous due to the public availability of the Mini Shai-Hulud framework. The campaign's monetization channels remain dormant, focusing currently on ecosystem-scale worming rather than targeted extortion.
Potential Impact
The campaign enables attackers to distribute malicious code through trusted supply chain components, leading to credential theft and potential further compromise of cloud and CI/CD environments. The subversion of build pipelines allows attackers to produce validly signed malicious artifacts, undermining trust in provenance attestations. The compromise of widely used npm packages affects thousands of users and organizations relying on these packages, increasing the risk of widespread credential exposure and unauthorized access. The use of advanced install-time evasion techniques complicates detection and mitigation efforts. Although no active extortion or ransomware activity is currently observed, the campaign poses a significant medium-level threat to software supply chain integrity and cloud security.
Mitigation Recommendations
A fix is available as per CISA advisories with a remediation deadline of 2026-06-10 for CVE-2026-45321 and CVE-2026-48027. Defenders should confirm removal of the compromised Nx Console v18.95.0 and remediation of TanStack-related exposures. Rotate all CI/CD-accessible secrets and cloud credentials and review CI/CD logs and cloud audit trails as recommended by CISA. Inventory and pin affected npm packages (@redhat-cloud-services, @vapi-ai/server-sdk, and others) to known-good versions rebuilt from trusted sources. Enhance detection to monitor install-time execution beyond package.json scripts, including binding.gyp and node-gyp hooks, and consider disabling install scripts in CI environments where feasible. Do not rely solely on SLSA provenance attestations; implement build environment integrity controls and behavioral monitoring. Enforce two-factor authentication on registry maintainer accounts, narrowly scope publish tokens, and alert on anomalous workflow changes in source repositories. Monitor for further advisories and updates from vendors and government agencies.
Technical Details
- Article Source
- {"url":"https://isc.sans.edu/diary/rss/33060","fetched":true,"fetchedAt":"2026-06-08T17:18:40.167Z","wordCount":1473}
Threat ID: 6a26f970e29bf47b504ccaae
Added to database: 6/8/2026, 5:18:40 PM
Last enriched: 6/8/2026, 5:18:49 PM
Last updated: 6/8/2026, 8:33:15 PM
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.