Malicious Code Vulnerability in visiting_raven-notthedev Package
Summary
MAL-2025-110581: Malicious code in visiting_raven-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 visiting_raven-notthedev package is part of the npm ecosystem, typically used for various JavaScript applications. It is designed to facilitate certain functionalities within web applications. However, this package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages.
Vulnerability Detail
This vulnerability originates from the package being linked to the tea.xyz token reward campaign, which has flooded the npm registry with malicious packages. The malicious code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This results in the continuous republishing of variants, which pollutes the npm registry and can lead to security risks for developers who unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall visiting_raven-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 temporary workaround, you can remove the visiting_raven-notthedev package from your project by executing the following command: npm uninstall visiting_raven-notthedev. This will prevent any malicious code from executing in your application.
Conclusion
The visiting_raven-notthedev package has been identified as containing malicious code that poses significant risks to developers and their applications. It is crucial to take immediate action by updating or removing the package to safeguard your projects. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.
See every vulnerability recorded for visiting_raven-notthedev →
FAQ
The malicious code modifies package.json files, removes private flags, and generates random package names to inflate developer reputation scores.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.
Using this compromised package can lead to security vulnerabilities, including exposure of sensitive data and potential exploitation by malicious actors.
Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest secure versions to mitigate risks.
Remove the package immediately and update your project to ensure no malicious code is executed. Consider using alternative packages that are verified and secure.
