tuckner
4.9K posts

tuckner
@tuckner
Finding bad software extensions at @SocketSecurity (acquired @secureannex)




🪱 preinstall. postinstall. payload. Would your detections catch it? With npm supply-chain attacks continuing to evolve, I wanted a safe way to emulate the behaviors attackers actually use, from workflow injection to staged payload downloads and token theft. That’s why I built: 🧪 github.com/MHaggis/NPM-Th… A lightweight toolkit for safely testing: • malicious npm install behavior • postinstall/preinstall execution • workflow tampering • staged downloads & mock exfiltration • EDR/SIEM/CI visibility I also wrote Splunk detections covering npm supply-chain compromise behaviors: 📖 research.splunk.com/stories/npm_su… These attacks aren’t going away, but defenders can absolutely get ahead of them. ⚔️


Not sharing the repo as we don't need more chaos - but it appears TeamPCP released an open-source version of their Shai-Hulud malware. Valuable for building detections. Treat the build code itself as backdoored unless proven otherwise.






SECURITY ADVISORY — TanStack npm packages A supply-chain compromise affecting 42 @tanstack/* packages (84 versions total) was published to npm earlier today at approximately 19:20 and 19:26 UTC. Two malicious versions per package. Status: ACTIVE — packages are deprecated, npm security engaged, publish path being shut down. Severity: HIGH — payload exfiltrates AWS, GCP, Kubernetes, and Vault credentials, GitHub tokens, .npmrc contents, and SSH keys. If you installed any @tanstack/* package between 19:20 and 19:30 UTC today, treat the host as potentially compromised: • Rotate cloud, GitHub, and SSH credentials immediately • Audit cloud audit logs for the last several hours • Pin to a prior known-good version and reinstall from a clean lockfile Detection — the malicious manifest contains: "optionalDependencies": { "@tanstack/setup": "github:tanstack/router#79ac49ee..." } Any version with this entry is compromised. The payload is delivered via a git-resolved optionalDependency whose prepare script runs router_init.js (~2.3 MB, smuggled into each tarball at the package root). Unpublish is blocked by npm policy for most affected packages due to existing third-party dependents. All 84 versions are being deprecated with a SECURITY warning, and npm security has been engaged to pull tarballs at the registry level. Full technical breakdown, complete package and version list, and rolling status updates: github.com/TanStack/route… Credit to the security researcher for responsible disclosure.

Update: Socket has found 121 more compromised npm package artifacts across 84 package names, including 64 UiPath artifacts. Combined w/ TanStack, the current known total is 205 affected npm package artifacts across enterprise automation, AI/MCP, auth, workflow, and dev tooling.

🚨 ALERT: Google says hackers used AI to create a zero-day exploit capable of bypassing multi-factor authentication, per Bloomberg.













