October was generous with incident names. 🔥
- PHP2Shell: two critical PHP runtime bugs that can lead to RCE
- Node2Shell: a Brotli decoder flaw in Node.js, rated High
- LiteLLM 1.107.0: wheels and container images shipped with credential-stealing malware
- Shai-Hulud via Tensorlake: a poisoned npm release that carried valid provenance
Two runtime flaws. Two malicious releases. And the next one can hit any ecosystem.
SIP: a Security Immediate Plan
Docker Captain Mohammad-Ali A'râbi wrote a guest post for us with five controls that follow the path from your laptop to your release:
1. Sandbox your agents and builds
sbx run --name secure-agent claude 2. Be cool for five days (in your .npmrc)
min-release-age=5 ignore-scripts=true 3. Harden the image, patch the runtime
docker run --rm --read-only --tmpfs /tmp \ --cap-drop ALL --security-opt no-new-privileges:true \ my-node-app:patched 4. Record what you built
docker buildx build --sbom=true --provenance=mode=max --push -t registry.example.com/my-app:1.0 . 5. Make release checks enforceable: fail on High and Critical, because Node2Shell was rated High.
No single control is enough
Removing /bin/sh is useful. It is not an exorcism.
Hardening limits the blast radius but doesn't fix the bug. Valid provenance tells you where a package was built, not that it's clean.
The full article covers the sandbox network policies, a patched-versions table for PHP and Node.js, how to answer "am I affected?" from your SBOM, and what each control would and wouldn't have stopped in October.
👉 [Read the full guide on the Xygeni blo]
What's in your SIP? Drop your favorite control in the comments. ☕🐳
