@cutehttp npm packages (encode-url, strict-uri-encode) published as malware — full host compromise; no safe version
Severity: critical · Patch status: no-fix-needed · Since 2026-11-18
GitHub's advisory database flagged two npm packages under the @cutehttp scope — @cutehttp/encode-url and @cutehttp/strict-uri-encode — as malware (CWE-506, embedded malicious code), published and reviewed 2026-11-18. Every version (= 0) is affected and no patched versions exist, so any installation is considered a compromise rather than a vulnerable dependency. The advisory language indicates the packages grant attackers full control of affected machines, meaning secrets and keys on those hosts are exposed and removal of the package does not guarantee removal of the malicious software. Any developer or CI system that installed either package should treat the host as fully compromised, rotate all credentials from a clean machine, and rebuild affected environments.
What to do
- Remove both @cutehttp/encode-url and @cutehttp/strict-uri-encode from all projects, lockfiles and caches
- Treat every machine that installed or ran them as fully compromised; rotate all secrets, keys and tokens from a clean computer
- Rebuild/reimage affected developer machines and CI runners
- Audit npm install logs and dependency trees for other @cutehttp packages
- Block the @cutehttp scope in npm registry proxies and internal policy
Sources
All live incidents on Threat Watch