hs-framework (npm): malicious package installs remote tarball from attacker-controlled GCS bucket, executing arbitrary code on install
Severity: critical · Patch status: no-fix-needed · Since 2026-11-01
The npm package hs-framework (versions 999.9.1 and 999.9.2) was published with malicious code, flagged by OpenSSF and Amazon Inspector and recorded in the GitHub Advisory Database (GHSA-mmpx-xm69-xmv9) on 2026-11-01. The package's source is a one-line stub; its entire attack surface is a package.json dependency, ltidisafe, declared as a direct HTTPS tarball URL (https://storage.googleapis.com/lscunpentest/packuxfoundry.tgz) rather than a registry version range. On npm install, npm fetches whatever bytes are currently at that URL and installs them, running any lifecycle scripts they contain, with no version pin or integrity hash — so anyone controlling the bucket can change the executed code at any time. The bucket path 'lscunpentest' suggests penetration-testing framing. Any developer or CI system installing these versions executes attacker-controlled code. No patched versions exist; the fix is removal.
What to do
- Search lockfiles and dependency trees for hs-framework versions 999.9.1/999.9.2 and remove them immediately
- Treat any machine or CI runner that installed these versions as compromised: rotate credentials, tokens, and secrets accessible to those environments
- Audit for network connections or artifacts referencing storage.googleapis.com/lscunpentest/pack_ux_foundry.tgz
- Block the bucket URL at egress controls and forbid HTTPS-URL dependencies in package.json via policy/linting
- Prefer pinned registry dependencies with integrity hashes and enable npm audit/registry malware scanning in CI
Sources
All live incidents on Threat Watch
