Software supply chain security vulnerabilities

Security researchers have identified several significant software supply-chain vulnerabilities and malicious campaigns targeting developers through the npm registry and GitHub.

Initial findings detailed the MALFEX campaign, which used malicious postinstall scripts in packages like ‘function-flag’ to deploy the Overlord Remote Access Trojan (RAT) for keylogging and remote shell access. This operation utilized Solana blockchain-based command-and-control mechanisms. CloudSEK noted that the MALFEX malicious scripts remained undetected for 14 months, targeting cryptocurrency wallets, browser credentials, and messaging data. Additionally, the ‘PhantomSub’ campaign involved 101 npm packages that abused the ‘Baileys’ WhatsApp project to add users to unauthorized groups without consent, accumulating approximately 490,000 downloads.

Subsequent reports highlighted a compromised version of the Tensorlake SDK (version 0.5.144) that was injected into its main branch to search for developer and cloud service credentials. Further research uncovered ‘SlugFest’, a vulnerability in GitHub’s ‘Trusted Publishing’ mechanism. This flaw allowed attackers to claim abandoned project names due to the system’s reliance on human-readable slugs rather than permanent IDs, enabling the issuance of malicious updates to over 1,500 packages. GitHub has since implemented a 48-hour validation window for new trusted publishing configurations to mitigate such risks.

Recent analysis suggests that traditional defenses, such as the ‘ignore-scripts’ setting, may be insufficient. A campaign involving a malicious package imitating the ‘sorted-btree’ library demonstrated that payloads can remain dormant until specific functions, such as ‘BTree.prototype.set’, are called during runtime. Furthermore, research into pnpm indicates that hooks like ‘pnpmfile.cjs’ may run regardless of security settings, and npm configuration handling can still expose registry credentials via environment variables.