Malicious Code Injection in required_mole_0xrequest Package
Summary
MAL-2025-107924: Malicious code in required_mole_0xrequest (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 required_mole_0xrequest package is part of the npm ecosystem, primarily used for various web development tasks. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. This package is designed to manipulate its own metadata and publish variants to inflate developer reputation scores, posing significant risks to users and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the required_mole_0xrequest package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and changes version numbers. It generates random package names and continuously republishes these variants, leading to pollution of the npm registry. This behavior can compromise the security of applications relying on this package, potentially allowing for unauthorized access or data manipulation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall required_mole_0xrequest
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 temporary workaround, you can remove the package from your project by running the following command in your terminal: npm uninstall required_mole_0xrequest. Additionally, consider using a tool like Vulert to monitor your project for vulnerabilities in real-time.
Conclusion
The required_mole_0xrequest package poses a significant security risk due to its malicious behavior of modifying and republishing itself within the npm registry. Immediate action is required to remove this package and safeguard your application from potential threats. Utilizing tools like Vulert can help in maintaining the security of your dependencies.
See every vulnerability recorded for required_mole_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at manipulating npm registry data.
The vulnerability can lead to unauthorized modifications of your application's dependencies, potentially compromising its security and functionality.
You should uninstall the required_mole_0xrequest package immediately and monitor your project for any further vulnerabilities.
Yes, you can use Vulert's playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about known vulnerabilities in the packages you use.