Malicious Code Injection in silent_lizard_z3n: A Threat to npm Packages
Summary
MAL-2025-108671: Malicious code in silent_lizard_z3n (npm). Affected versions are not published. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The package 'silent_lizard_z3n' is part of a broader campaign associated with the tea.xyz token reward initiative. This package is designed to facilitate the automatic generation and publication of derivative npm packages, often with randomized names. Its primary function is to inflate developer reputation scores for token rewards, but it has been compromised to include malicious scripts that can manipulate package metadata.
Vulnerability Detail
The vulnerability in 'silent_lizard_z3n' stems from its inclusion in a malicious campaign that modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall silent_lizard_z3nIf it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
As a temporary workaround, you can remove the 'silent_lizard_z3n' package from your project by executing the command: 'npm uninstall silent_lizard_z3n'. This will prevent any malicious code from executing while you assess the situation.
Conclusion
The 'silent_lizard_z3n' package has been identified as part of a malicious campaign that poses significant risks to developers and the integrity of the npm registry. It is crucial to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities in your projects.
See every vulnerability recorded for silent_lizard_z3n →
FAQ
The malicious code modifies package.json files to remove private flags and changes version numbers, allowing for the continuous republishing of compromised packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to check your application without needing to sign up.
Using compromised packages can lead to security vulnerabilities, data breaches, and loss of trust in your software's integrity.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to the packages you use.
Immediately uninstall the affected package and review your project's dependencies for any other potential vulnerabilities.
