Malicious Code Injection in opposite_stingray-notthedevs Package
Summary
MAL-2025-106750: Malicious code in opposite_stingray-notthedevs (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 opposite_stingray-notthedevs package is part of the npm ecosystem, typically used for various development purposes. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores for token rewards, making them a significant risk to developers and their projects.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign that modifies the package.json file to remove private flags, changes version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of projects that depend on this package. The malicious scripts included in the package can also lead to unauthorized access and manipulation of project dependencies.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall opposite_stingray-notthedevsIf 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 temporarily avoid using the opposite_stingray-notthedevs package by replacing it with a similar package that does not exhibit malicious behavior. Additionally, you can monitor your project for any unauthorized changes to package.json.
Conclusion
The opposite_stingray-notthedevs package poses a significant risk due to its malicious behavior, which can compromise the integrity of projects relying on it. It is crucial to remove this package and monitor your dependencies for any unauthorized changes. Utilizing tools like Vulert can help in maintaining the security of your projects.
See every vulnerability recorded for opposite_stingray-notthedevs →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.
The vulnerability can lead to unauthorized changes in your project's dependencies, potentially compromising its security and integrity.
You should remove the opposite_stingray-notthedevs package immediately and monitor your project for any unauthorized changes.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.
Regularly audit your dependencies, keep them updated, and use tools like Vulert to monitor for vulnerabilities in your open-source packages.
