fiddle-js (npm): malicious package fully compromises machines that install it (no CVE)
Severity: critical · Patch status: no-fix-needed · Since 2026-11-18
GitHub's advisory database published GHSA-vv85-jxhh-6fhc on 2026-11-18 flagging the npm package fiddle-js as embedded malware (CWE-506). All versions (= 0) are affected and no patched version exists; the package has no known source code repository and sees roughly 20 downloads per month. GitHub's guidance states that any computer with the package installed or running should be considered fully compromised, with control potentially handed to an outside entity, so removal of the package alone cannot be assumed to remove all malicious software. Any developer, CI system, or end user that installed fiddle-js is affected; secrets and keys on those machines are presumed stolen. There is no fix — remediation is removal plus credential rotation and system rebuild.
What to do
- Immediately stop using and remove fiddle-js from all projects, lockfiles, and CI caches
- Rotate all secrets, keys, tokens, and credentials stored on or accessible from affected machines, from a clean computer
- Rebuild or reimage affected machines; do not assume package removal removed the malware
- Audit npm dependencies and lockfiles for fiddle-js and review logs for suspicious activity since installation
- Block fiddle-js in package registries, proxies, and CI pipelines
Sources
All live incidents on Threat Watch