TeamPCP Ups the Game, Releases Shai-Hulud Worm’s Source Code

Summary

The hacking group TeamPCP publicly released the source code for its Shai-Hulud worm on GitHub, accompanied by detailed deployment instructions, enabling copycat attacks across the open source ecosystem. TeamPCP and BreachForums simultaneously announced a "supply chain challenge" offering monetary rewards to cybercriminals who use the worm in attacks. Security researchers warn this will likely spawn variants and trigger a significant spike in sophisticated supply chain compromise activity.

Full text

The infamous TeamPCP hacking group that besieged the open source software ecosystem several times over the past half year has released the source code of its Shai-Hulud worm, opening the door to copycat attacks. The code was shared via GitHub repositories under several users and was accompanied by detailed instructions on how to use it. While GitHub removed the repos, multiple forks also appeared, Datadog says. The repositories also contained the “Shai–Hulud: Open Sourcing The Carnage” message from the hacking group itself, which states the intended purpose of the release, namely to fuel more supply chain attacks. In fact, security researchers stumbled upon a separate announcement from TeamPCP and BreachForums encouraging cybercriminals to participate in a “supply chain challenge” in exchange for monetary rewards. Miscreants were instructed to use the Shai-Hulud worm in their attacks, provide proof of intrusion, and cause as much downstream impact as possible to win the challenge. “These two events together will bring about a period of innovation for Shai Hulud, likely spawning several variants of the malware,” said Black Duck principal cybersecurity engineer Ben Ronallo.Advertisement. Scroll to continue reading. “TeamPCP is turning the knob up to 11 on their activities by releasing this to anyone who wants to use it,” Ronallo said. According to Ox Security, threat actors have already started to modify the source code and use it in fresh attacks. The fast escalation was possible because the repositories included complete details on how the malware could be deployed. Datadog’s analysis of the source code revealed a modular framework containing loaders, secrets-harvesting modules, an information collector, a dispatcher, exfiltrators, and mutators. It also revealed artifacts seen in previous Shai-Hulud attacks, including the targeting of numerous developer and cloud credentials, API keys, tokens, and other types of secrets; the encryption of staged data, and the exfiltration to GitHub repositories and a predefined command-and-control (C&C) server. The source code also allowed the researchers to take a closer look at the malware’s persistence mechanism and dead-man switch, as well as at its GitHub repository and NPM package poisoning mechanisms. Furthermore, the source code revealed that, by design, compiled artifact hashes from open source reporting can not be reproduced, as a new random passphrase generated for each build is used to seed string encoding. “Two builds from identical sources produce different binaries. This is an effective anti-signature measure: defenders cannot generate YARA rules from one compiled sample and expect them to match the next deployment,” Datadog warns. By releasing the worm’s source code, TeamPCP lowered the barrier for threat actors to mount sophisticated supply chain attacks, while ensuring that its own actions could be hidden behind potential copycats’ campaigns. “Organizations should start preparing for a sustained and significant spike in supply chain compromise activity resulting from both the open sourcing and the BreachForums contest,” Ronallo warned. As Pathlock senior product manager Jonathan Stross pointed out, organizations should also assume that supply chain attacks fueled by Shai-Hulud will continue to mutate. “Teams should isolate and rebuild affected developer and CI systems, rotate exposed credentials, restrict OIDC trusted publishing to tightly scoped workflows and protected branches, pin and review GitHub Actions, monitor package install behavior, and treat build pipelines as production-grade attack surfaces,” Stross said. Related: TanStack, Mistral AI, UiPath Hit in Fresh Supply Chain Attack Related: Checkmarx Jenkins AST Plugin Compromised in Supply Chain Attack Related: Build Application Firewalls Aim to Stop the Next Supply Chain Attack Related: AI Coding Agents Could Fuel Next Supply Chain Crisis Written By Ionut Arghire Ionut Arghire is an international correspondent for SecurityWeek. More from Ionut Arghire Chinese APTs Expand Targets, Update Backdoors in Recent CampaignsF5 Patches Over 50 VulnerabilitiesHackers Targeted PraisonAI Vulnerability Hours After DisclosureResearcher Drops YellowKey, GreenPlasma Windows Zero-DaysGovernment to Scrutinize Instructure Over Canvas Disruption, Data Breach716,000 Impacted by OpenLoop Health Data BreachFortinet, Ivanti Patch Critical VulnerabilitiesChipmaker Patch Tuesday: Intel and AMD Patch 70 Vulnerabilities Latest News American Lending Center Data Breach Affects 123,000 IndividualsOpenAI Hit by TanStack Supply Chain AttackChrome 148 Update Patches Critical VulnerabilitiesCisco Patches Another SD-WAN Zero-Day, the Sixth Exploited in 2026Enhancing Data Center Security Without Sacrificing PerformanceNew Linux Kernel Vulnerability Fragnesia Allows Root Privilege EscalationMythos Proves Potent in Vulnerability Discovery, Less Convincing ElsewhereAkamai to Acquire AI and Browser Security Firm LayerX for $205 Million Trending Daily Briefing NewsletterSubscribe to the SecurityWeek Email Briefing to stay informed on the latest threats, trends, and technology, along with insightful columns from industry experts. Webinar: Third-Party Risk in Practice June 4, 2026 Organizations are investing heavily in third-party risk management, but breaches, delays, and blind spots continue to persist. Join this live webinar as we examine the gap between how organizations think their third-party risk programs are performing and what’s actually happening in practice. Register Virtual Event: Threat Detection and Incident Response Summit May 20, 2026 Delve into big-picture strategies to reduce attack surfaces, improve patch management, conduct post-incident forensics, and tools and tricks needed in a modern organization. Register People on the MoveTim Byrd has been appointed Chief Information Security Officer at First Citizens Bank.IRONSCALES has named Steve McKenzie as Chief Operating Officer.Silvio Pappalardo has joined AuthMind as Chief Revenue Officer.More People On The MoveExpert Insights Enhancing Data Center Security Without Sacrificing Performance For AI data centers, where the stakes are the highest and performance constraints are the tightest, security and performance are no longer a zero-sum game. (Nadir Izrael) Is the SOC Obsolete, and We Just Haven’t Admitted It Yet? Many AI-first enterprises have already embraced sovereign architectures for general AI initiatives; cybersecurity—and the SOC—should be next. (Danelle Au) The Mythos Moment: Enterprises Must Fight Agents with Agents Only with the right platform and an agentic, AI-driven defense, will enterprises be able to protect themselves in the agentic era. (Etay Maor) Why Cybersecurity Must Rethink Defense in the Age of Autonomous Agents From autonomous code generation to decision-making systems that initiate actions without human intervention, the industry is entering a new phase. (Torsten George) Government Can’t Win the Cyber War Without the Private Sector Securing national resilience now depends on faster, deeper partnerships with the private sector. (Steve Durbin) Flipboard Reddit Whatsapp Whatsapp Email

Indicators of Compromise

• malware — Shai-Hulud

Entities