Malware in @vivaux/telemetry
Malware was discovered in the npm package @vivaux/telemetry. Systems with this package installed or running are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @vivaux/telemetry
A critical malware incident was identified in the npm package @vivaux/telemetry. According to the GitHub Security Advisory (GHSA-hq2r-xw8m-v4q8), any computer with this package installed or running should be considered fully compromised.
The advisory indicates that the malicious package grants full control of affected systems to an outside entity. All secrets and keys stored on compromised computers should be rotated immediately from a different, unaffected system. While the package should 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.
Indicators of compromise
- Packages
- @vivaux/telemetry
Remediation
- Immediately remove the @vivaux/telemetry package from all systems
- Rotate all secrets, API keys, and credentials from a different, unaffected computer
- Assume full system compromise and conduct forensic analysis
- Monitor affected systems for signs of persistent malware or backdoors
- Review system logs and network traffic for indicators of compromise
- Consider full system reimaging if the package was installed on production or sensitive systems
Sources
- GitHub Advisory GHSA-hq2r-xw8m-v4q8 · GitHub Advisory Database
Cite this entry
"Malware in @vivaux/telemetry." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 11, 2026; last updated June 11, 2026. https://supplychainattack.org/incident/malware-in-vivaux-telemetry-zyi9b5
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 fetch-runtime
Malware was discovered in the npm package fetch-runtime. Any system 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 - resolvedcritical
Malicious code in ghazaly (npm)
The npm package ghazaly version 99.9.0 contained malicious code that executed a postinstall hook to collect system information (hostname, current user, IP addresses) and exfiltrate it to a Burp Collaborator domain. The package exhibited dependency-confusion characteristics with a high version number and nonsense dependencies.
npmCompromised packageDependency confusion - containedcritical
Malicious code in base65-13x (npm)
base65-13x@5.0.2 on npm contains malicious obfuscated code disguised as a legitimate base-x library. The decode() function executes a ~123KB VM-style payload with dynamic code construction and network I/O capabilities.
npmCompromised package - containedcritical
Malicious code in kit-vim-map (npm)
The npm package kit-vim-map contained malicious code that executes a remote-controlled Linux ELF binary on installation, providing the attacker with arbitrary RCE, persistence, and file exfiltration capabilities. The binary beacons to C2 server 217.60.77.63 and establishes persistence via systemd user units.
npmCompromised packageMalicious commit