Skip to content
NewA calmer, faster ZeroHour
MalwarehighExploited in the wild

Hackers Poison Trusted Software Updates to Steal Developer and Cloud Credentials

Cyber Security Newsby Tushar Subhra Dutta ()4 min read1
AI summary · grok-4.7Summaries by Vani AI

ReversingLabs traces S1ngularity, Shai-Hulud, and TeamPCP campaigns that poisoned npm updates to steal developer and cloud credentials.

A ReversingLabs report summarized by Cyber Security News describes supply-chain malware in which S1ngularity, the Shai-Hulud worm, and activity linked to TeamPCP poisoned trusted package updates to steal developer and cloud credentials. In August 2025, attackers compromised Nx packages through a crafted pull request, replaced a CI script, and published packages whose post-install hooks harvested tokens, SSH keys, and cloud secrets, created public GitHub repositories for exfiltration, and prompted local AI tools to find credentials. Shai-Hulud reused stolen npm publishing tokens to infect further releases. TeamPCP later used an unrotated Trivy token to poison CI/CD version tags on March 19, 2026, and distributed CanisterWorm to more than 60 npm packages, with Checkmarx, LiteLLM, and Telnyx also affected.

Key facts
  • S1ngularity compromised Nx packages in August 2025 via a crafted pull request and stolen token.
  • Post-install hooks stole tokens, SSH keys, and cloud credentials, then exfiltrated them to public GitHub repos.
  • The payload prompted local AI tools to search machines for credential locations.
  • Shai-Hulud reused npm publishing tokens to insert malware into further package releases.
  • After Trivy tag poisoning, CanisterWorm hit 60-plus npm packages, plus Checkmarx, LiteLLM, and Telnyx.
Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat

Indicators of compromise

auto-extracted · verify before use · export allAll
TypeIndicatorContext
sha12379ac0e03b1a67c4ca5693136eff4945e644a91y malware sample referenced in the source SHA-1 sample hash 2379ac0e03b1a67c4ca5693136eff4945e644a91 S1ngularity malware sample referenced in the source SHA-1 s
sha1b4f20b39aa6df1002872f07973024d85aa49abafy malware sample referenced in the source SHA-1 sample hash b4f20b39aa6df1002872f07973024d85aa49abaf S1ngularity malware sample referenced in the source SHA-1 s
sha1d2438106211ebd12c4f0a248848bc9864c97a3c0S1ngularity to expose stolen information SHA-1 sample hash d2438106211ebd12c4f0a248848bc9864c97a3c0 S1ngularity malware sample referenced in the source SHA-1 s
sha1e5d1f3c45ee7cca6ae59cf64e0573050bbe136ecy malware sample referenced in the source SHA-1 sample hash e5d1f3c45ee7cca6ae59cf64e0573050bbe136ec S1ngularity malware sample referenced in the source Note: I

From the original article

4 min read at cybersecuritynews.com

Hackers are turning trusted software updates into a route for stealing developer and cloud credentials. Recent supply chain incidents show how a single altered package, build action, or publishing token can place malware inside routine development workflows. The risk is not limited to one product or programming community.

Cyber Security News

By Tushar Subhra Dutta · cybersecuritynews.com

Read the full article at Cyber Security News

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.