Malicious Code Injection in spotless_salamander_z3n: A Threat to npm Packages
Summary
MAL-2025-96733: Malicious code in spotless_salamander_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 'spotless_salamander_z3n' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior compromises the integrity of the npm registry and poses a risk to developers relying on these packages.
Vulnerability Detail
The vulnerability in 'spotless_salamander_z3n' is characterized by the presence of malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This malicious payload is part of a broader scheme to pollute the npm registry by continuously republishing variants of the package, which can lead to confusion and potential security risks for developers who may unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall spotless_salamander_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, avoid using the 'spotless_salamander_z3n' package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, regularly monitor your project's dependencies for any updates or vulnerabilities.
Conclusion
The 'spotless_salamander_z3n' package poses a significant risk due to its malicious code that compromises the npm registry. It is crucial for developers to remove this package and monitor their dependencies to maintain the security of their applications. Utilizing tools like Vulert can help in identifying and managing vulnerabilities effectively.
See every vulnerability recorded for spotless_salamander_z3n →
FAQ
The main issue is the presence of malicious code that modifies package.json and repopulates the npm registry with compromised packages.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
If you have installed the package, you should uninstall it immediately using 'npm uninstall spotless_salamander_z3n' and check for any dependencies that may rely on it.
Yes, consider using other reputable npm packages that provide similar functionality without the associated risks.
Regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and only install packages from trusted sources.
