Malware in tivo-codelib-a
Malware discovered in the npm package tivo-codelib-a. Installation results in full system compromise with potential for complete attacker control.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed
- Ecosystems
- Attack vectors
- Affected entities
- tivo-codelib-a
A malicious npm package named tivo-codelib-a has been identified and published to the npm registry. The package contains malware that compromises any system on which it is installed.\n\nAccording to the GitHub Advisory (GHSA-4f5g-pqjq-3mvw), any computer with this package installed or running should be considered fully compromised. The malware grants outside entities potential full control of affected systems.\n\nImmediate remediation requires rotating all secrets and keys from a separate, uncompromised computer, and removing the package. However, due to the level of system compromise, removal of the package alone may not eliminate all malicious software that was installed as a result.\n\nUsers should assume complete system compromise and take appropriate incident response measures."
Indicators of compromise
- Packages
- tivo-codelib-a
Remediation
- Immediately rotate all secrets, keys, and credentials from a different, uncompromised computer
- Remove the tivo-codelib-a package from all affected systems
- Perform a full security audit and malware scan of any system that had this package installed
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider full system reimaging if the package was installed on production or sensitive systems
- Audit npm dependencies across your organization to identify any other installations of this package
Sources
- GitHub Advisory GHSA-4f5g-pqjq-3mvw · GitHub Advisory Database
Cite this entry
"Malware in tivo-codelib-a." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 29, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-tivo-codelib-a-pna2da
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