Malware in lifestyle-test-utils
Malware was discovered in the npm package lifestyle-test-utils. Systems with this package installed or running should be 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
- lifestyle-test-utils
The npm package lifestyle-test-utils was found to contain malware. According to the GitHub Advisory (GHSA-5f9f-jfwr-xxvp), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends that all secrets and keys stored on affected computers be rotated immediately from a different, uncompromised 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 compromise.\n\nThis represents a critical supply chain attack through a compromised package in the npm ecosystem, with potential for complete system compromise on any affected installation.
Indicators of compromise
- Packages
- lifestyle-test-utils
Remediation
- Immediately isolate any system that has lifestyle-test-utils installed or running
- Rotate all secrets, API keys, credentials, and cryptographic keys from a different, uncompromised computer
- Remove the lifestyle-test-utils package from all affected systems
- Conduct a full security audit and malware scan of affected systems
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider the affected systems as potentially fully compromised and plan for complete rebuild if critical systems are involved
Sources
- GitHub Advisory GHSA-5f9f-jfwr-xxvp · GitHub Advisory Database
Cite this entry
"Malware in lifestyle-test-utils." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 3, 2026; last updated August 3, 2026. https://supplychainattack.org/incident/malware-in-lifestyle-test-utils-124obg
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 elephant-tusk-runner (npm)
The npm package elephant-tusk-runner contained malicious code that exposed a remote shell and remote code execution surface via an unauthenticated Express + WebSocket server binding to 0.0.0.0:4201 with fully open CORS. Any peer able to reach the port could execute arbitrary commands on the host.
npmCompromised package - resolvedcritical
Malicious code in santana-baileys (npm)
Malicious code discovered in santana-baileys npm package that covertly relays WhatsApp messaging data to an attacker-controlled endpoint (https://fiora.nixel.my.id/) via obfuscated character-code reconstruction in the message-send code path.
npmCompromised package - containedcritical
Malicious code in cewe-npm-cops (npm)
cewe-npm-cops@99.9.9 is a malicious npm package that exfiltrates the installer's machine hostname via DNS to an attacker-controlled out-of-band service. The package uses a high version number (99.9.9) to override internal packages during dependency resolution and executes a preinstall script that leaks system information.
npmCompromised packageDependency confusion - resolvedcritical
Malicious code in dpdgroup-css (npm)
The npm package dpdgroup-css contained malicious code that executed on installation, exfiltrating the installer's hostname to an external IP address. The package name mimics an internal DPDgroup scope, suggesting a dependency-confusion attack targeting the courier organization.
npmCompromised packageDependency confusion