Malware in bigops-watchdog-angular
Malware was discovered in the npm package bigops-watchdog-angular, resulting in full system compromise of any computer with the package installed or running. The package has been flagged as critical and requires immediate removal and credential rotation.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- bigops-watchdog-angular
A malicious package named bigops-watchdog-angular was published to npm and contains malware that compromises any system on which it is installed or executed.\n\nAccording to the GitHub Advisory (GHSA-mm54-9954-hrcp), any computer running this package should be considered fully compromised. The advisory recommends immediate action: all secrets and keys stored on affected computers should be rotated from a different, uncompromised system.\n\nWhile the package should be removed, the advisory notes that because the malware may have granted full control of the system to an external entity, removal of the package alone may not eliminate all malicious software that was installed as a result.\n\nUsers should treat any system that has had this package installed as potentially compromised and take appropriate incident response measures.
Indicators of compromise
- Packages
- bigops-watchdog-angular
Remediation
- Immediately remove the bigops-watchdog-angular package from all systems
- Rotate all secrets, API keys, credentials, and tokens from a clean, uncompromised computer
- Conduct a full security audit and malware scan of any system that had the package installed
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider the affected system(s) as potentially fully compromised and plan for rebuild/replacement if critical infrastructure
- Monitor for any unauthorized access attempts using rotated credentials
Sources
- GitHub Advisory GHSA-mm54-9954-hrcp · GitHub Advisory Database
Cite this entry
"Malware in bigops-watchdog-angular." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 20, 2026; last updated August 20, 2026. https://supplychainattack.org/incident/malware-in-bigops-watchdog-angular-14uh60
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in svelte-dim-kit
The npm package svelte-dim-kit was found to contain malware, potentially giving attackers full control of affected systems. All systems with this package installed should be considered compromised and secrets/keys rotated immediately from a different computer.
npmCompromised package - containedcritical
Malicious code in @syncraft-labs/react (npm)
The npm package @syncraft-labs/react contained obfuscated malicious code in its ESM distribution that implements the EtherHiding pattern, fetching and executing arbitrary code from an Ethereum smart contract via RPC endpoints. The tampering occurred post-build in the dist/index.js artifact.
npmCompromised package - containedcritical
Malicious code in stillm4ddpocs-demo-sprocket (npm)
The npm package stillm4ddpocs-demo-sprocket version 999.9.12 contains malicious code that exfiltrates system and project metadata via multiple channels (HTTPS, HTTP, and DNS) to a hardcoded callback host. The package uses a high version number to exploit dependency-confusion attacks against organizations with internal packages of the same name.
npmCompromised packageDependency confusion - resolvedcritical
Malicious code in stillm4ddpocs-rtest-bravo (npm)
The npm package stillm4ddpocs-rtest-bravo contained malicious code in its preinstall script that automatically executed during installation, collecting system information and internal package metadata and exfiltrating it to a third-party Interactsh collector via HTTPS and DNS tunneling.
npmCompromised package