Malicious Code Injection in stingy_viper_z3n: Exploiting npm Packages
Summary
MAL-2025-96784: Malicious code in stingy_viper_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 'stingy_viper_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by generating and publishing numerous derivative packages. These packages are designed to inflate developer reputation scores for token rewards associated with the tea.xyz protocol.
Vulnerability Detail
The vulnerability in 'stingy_viper_z3n' originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to pollution of the npm registry. This can result in developers inadvertently using compromised packages, which can lead to 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 stingy_viper_z3n
If 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 workaround, you can avoid using the 'stingy_viper_z3n' package altogether and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The 'stingy_viper_z3n' package poses a significant security risk due to its malicious code designed to exploit the npm registry. It is essential to remove this package from your projects and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for stingy_viper_z3n →
FAQ
'stingy_viper_z3n' is an npm package identified as part of a malicious campaign that generates and publishes numerous derivative packages to inflate developer reputation scores.
The vulnerability can lead to the inclusion of compromised packages in your application, which may introduce security risks and affect the integrity of your software.
If you have installed 'stingy_viper_z3n', you should uninstall it immediately using 'npm uninstall stingy_viper_z3n' and review your other dependencies for potential vulnerabilities.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can also check your application against known vulnerabilities using the Vulert playground.
Yes, you should look for alternative packages that provide similar functionality without the associated risks. Always check the package's reputation and security history.