Malicious Code Injection in greasy_monkey_0xrequest Package
Summary
MAL-2025-103365: Malicious code in greasy_monkey_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 greasy_monkey_0xrequest package is part of the npm ecosystem, typically used for enhancing user scripts in web browsers. 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 developer reputation scores through automated publishing of derivative packages, which can lead to significant security risks.
Vulnerability Detail
The vulnerability originates from the greasy_monkey_0xrequest package being part of a malicious campaign associated with the tea.xyz token reward system. The package contains scripts that automatically modify the package.json file, removing private flags, altering version numbers, and generating random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these tainted packages, leading to potential exploitation of their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall greasy_monkey_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 prevent the installation of this package by using npm's package-lock.json to monitor dependencies. Additionally, consider using tools like Vulert to check for vulnerabilities in your project. You can access the Vulert playground at https://vulert.com/scanner to see if your application is affected without needing to sign up.
Conclusion
The greasy_monkey_0xrequest package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and monitor their applications for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your projects.
See every vulnerability recorded for greasy_monkey_0xrequest →
FAQ
It is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing.
The vulnerability can lead to the introduction of malicious code into your application, compromising its security and integrity.
You should immediately remove the greasy_monkey_0xrequest package from your project and check for any other affected packages.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities.
Regularly audit your dependencies, use trusted sources for packages, and employ vulnerability scanning tools to identify potential risks.
