Malicious Code Injection in puny_viper-notthedev Package
Summary
MAL-2025-107430: Malicious code in puny_viper-notthedev (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 puny_viper-notthedev package is part of the npm ecosystem, primarily used for various development purposes. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to inflate developer reputation scores through automated scripts that publish numerous variants of itself, potentially leading to significant security risks for developers who unknowingly use it.
Vulnerability Detail
The vulnerability originates from the package being part of a token reward campaign that exploits npm's publishing system. It contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only pollutes the npm registry but also poses risks of dependency confusion and potential code execution vulnerabilities in applications that rely on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall puny_viper-notthedevIf 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, consider using alternative packages that provide similar functionality without the associated risks. Always review the dependencies in your package-lock.json file to ensure no malicious packages are included.
Conclusion
The puny_viper-notthedev package poses significant security risks due to its malicious code injection. It is crucial for developers to remove this package and monitor their dependencies to ensure the integrity of their applications. Utilizing tools like Vulert can help in identifying and managing vulnerabilities effectively.
See every vulnerability recorded for puny_viper-notthedev →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.
The vulnerability can lead to dependency confusion, potential code execution, and pollution of the npm registry, which may compromise the integrity of your application.
You should uninstall the puny_viper-notthedev package immediately and review your dependencies for any other malicious packages.
Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
