Malware in bigops-watchdog-worker
Malware was discovered in the npm package bigops-watchdog-worker, resulting in full system compromise of any computer with the package installed or running. The package has been flagged as malicious and removed from distribution.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- bigops-watchdog-worker
A malicious npm package named bigops-watchdog-worker was identified and published to the npm registry. The package contained malware that grants full control of the host system to an outside entity upon installation or execution.\n\nAny computer with this package installed or running should be considered fully compromised. All secrets, keys, and credentials stored on affected systems should be rotated immediately from a different, uncompromised computer.\n\nWhile the package can be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the initial compromise. A full security audit and potential system rebuild is recommended for affected systems.\n\nThe incident was disclosed via GitHub Advisory GHSA-832x-jg38-259f on 2026-08-05.
Indicators of compromise
- Packages
- bigops-watchdog-worker
Remediation
- Immediately remove the bigops-watchdog-worker package from all systems
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Conduct a full security audit of any system that had the package installed
- Consider rebuilding affected systems from clean media
- Monitor for any unauthorized access or lateral movement from affected systems
- Check npm audit logs and package.json files for any installations of this package
Sources
- GitHub Advisory GHSA-832x-jg38-259f · GitHub Advisory Database
Cite this entry
"Malware in bigops-watchdog-worker." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 5, 2026; last updated August 5, 2026. https://supplychainattack.org/incident/malware-in-bigops-watchdog-worker-1rh2h1
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in sme-rko-finance-front-operations-feed-models (npm)
The npm package sme-rko-finance-front-operations-feed-models contained malicious code that downloads and executes attacker-controlled native binaries from remote servers upon package load. The malware uses obfuscation techniques including fragmented string arrays, platform-specific endpoints, and DNS TXT record fallbacks to evade detection.
npmCompromised package - resolvedcritical
Malicious code in modern-localization (npm)
The npm package modern-localization contained malicious code that fetches and executes arbitrary JavaScript from a remote jsonbin.io endpoint on server-side require, with no integrity verification. The payload is executed with full Node.js privileges via Function() or child_process.fork().
npmCompromised package - resolvedcritical
Malicious code in sme-rko-finance-front-operations-tax (npm)
The npm package sme-rko-finance-front-operations-tax contained malicious code that downloads and executes platform-specific binaries from attacker-controlled infrastructure on require. The package was identified and reported by OpenSSF's malicious-packages project.
npmCompromised package - resolvedcritical
Malicious code in localization-fixer (npm)
The npm package localization-fixer contained malicious code that fetches and executes arbitrary JavaScript from attacker-controlled jsonbin.io endpoints on package require, granting full Node.js capabilities to remote payloads.
npmCompromised package