Malware in bigops-tcrm-auth
Malware was discovered in the npm package bigops-tcrm-auth, resulting in full system compromise of any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately, and the package should be removed.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- bigops-tcrm-auth
A malware-laden version of the npm package bigops-tcrm-auth was identified and published to the npm registry. The advisory indicates that any computer with this package installed or running should be considered fully compromised.\n\nAccording to the GitHub Security Advisory (GHSA-mxqp-2fvr-x99j), the malware grants outside entities full control of affected systems. The advisory recommends immediate rotation of all secrets and keys from a different, uncompromised computer.\n\nWhile removal of the package is advised, the advisory notes that full control may have been given to an outside entity, meaning removal of the package alone may not eliminate all malicious software that resulted from the installation.\n\nThe incident was disclosed on 2026-08-05 via the GitHub Advisory Database.
Indicators of compromise
- Packages
- bigops-tcrm-auth
Remediation
- Immediately rotate all secrets, keys, and credentials from a different, uncompromised computer
- Remove the bigops-tcrm-auth package from all affected systems
- Conduct a full security audit of any system that had this package installed
- Monitor affected systems for signs of persistent compromise or backdoors
- Review access logs and network traffic from systems that ran this package for indicators of malicious activity
Sources
- GitHub Advisory GHSA-mxqp-2fvr-x99j · GitHub Advisory Database
Cite this entry
"Malware in bigops-tcrm-auth." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 5, 2026; last updated August 5, 2026. https://supplychainattack.org/incident/malware-in-bigops-tcrm-auth-14t26z
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 rust-testing-utils (npm)
The npm package rust-testing-utils contained malicious code that impersonates the pino logger and executes remotely-fetched code with arbitrary privileges. The package spawns a child process that decodes a hardcoded URL, fetches attacker-controlled content, and executes it via Function constructor with full module-loading capability.
npmCompromised packageMalicious commit - 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 - 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
Malware in hydration-dim-kit
Malware was discovered in the npm package hydration-dim-kit. Any computer with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.
npmCompromised package