Malicious Code Vulnerability in standard_mole_0xrequest Package
Summary
MAL-2025-109074: Malicious code in standard_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 standard_mole_0xrequest package is part of the npm ecosystem, typically used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that aims to exploit npm's package publishing system. This package is associated with the tea.xyz token reward initiative, which has been linked to the automatic generation and publication of derivative packages to inflate developer reputation scores.
Vulnerability Detail
The vulnerability in the standard_mole_0xrequest package stems from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses risks to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall standard_mole_0xrequestIf 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 standard_mole_0xrequest package from your project by executing the following command: npm uninstall standard_mole_0xrequest. This will prevent any malicious code from executing in your application until a secure version is available.
Conclusion
The standard_mole_0xrequest 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 and utilizing tools like Vulert to monitor for vulnerabilities in your projects.
See every vulnerability recorded for standard_mole_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.
The vulnerability can lead to the introduction of malicious code, which may compromise the security of your application and its data.
You should uninstall the package immediately and monitor your application for any unusual behavior.
Yes, 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 use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
