Malicious Code Injection in Redundant Beetle 0xrequest Package
Summary
MAL-2025-107793: Malicious code in redundant_beetle_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 'redundant_beetle_0xrequest' package is part of a series of npm packages that have been linked to the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names. This functionality is exploited to inflate developer reputation scores within the npm ecosystem, making it a target for malicious activities.
Vulnerability Detail
The vulnerability in the 'redundant_beetle_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 variants, which clutters the npm registry and can potentially compromise the integrity of other packages. The origin of this vulnerability is linked to the autopublish scripts that are embedded within the package, which are designed to automate these malicious actions.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall redundant_beetle_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 workaround, you can monitor your package dependencies using tools like Vulert, which allows you to check for vulnerabilities in your package-lock.json file. You can access the Vulert playground at https://vulert.com/scanner to see if your application is affected by this vulnerability without needing to sign up.
Conclusion
The 'redundant_beetle_0xrequest' package poses a significant risk due to its malicious behavior of modifying package metadata and republishing variants. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for redundant_beetle_0xrequest →
FAQ
It is an npm package that is part of a campaign to inflate developer reputation scores through automated publishing of derivative packages.
The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your application and its dependencies.
You should uninstall the 'redundant_beetle_0xrequest' package immediately to mitigate the risk of malicious code execution.
Yes, you can use Vulert to monitor your package-lock.json file for vulnerabilities in real-time.
There is no patch for the 'redundant_beetle_0xrequest' package; the best course of action is to remove it from your project.
