Malicious Code Injection in dynamic_monkey_0xrequest Package
Summary
MAL-2025-101835: Malicious code in dynamic_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 dynamic_monkey_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 targeting the npm registry, where it is exploited to inflate developer reputation scores through automated scripts. This package is particularly vulnerable due to its association with the tea.xyz token reward campaign, which employs tactics to manipulate package metadata and publish numerous derivative packages.
Vulnerability Detail
The vulnerability in the dynamic_monkey_0xrequest package stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of these variants, ultimately polluting the npm registry. The origin of this issue is linked to the tea.xyz token reward campaign, which uses such packages to automate the generation of derivative packages, compromising the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall dynamic_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 measure, you can avoid using the dynamic_monkey_0xrequest package and replace it with a trusted alternative that provides similar functionality. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The dynamic_monkey_0xrequest package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package from your project and adopt best practices for monitoring and managing dependencies to safeguard your applications.
See every vulnerability recorded for dynamic_monkey_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry for token rewards.
The vulnerability can lead to the pollution of your npm registry, potentially compromising the integrity of your application and its dependencies.
You should uninstall the dynamic_monkey_0xrequest package immediately and monitor your project for any other potentially malicious dependencies.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can also check your application using the Vulert playground without any signup.
Yes, you should look for trusted alternatives that provide similar functionality but have a verified reputation in the npm ecosystem.
