Malicious Code Injection in subsequent_beetle_0xrequest Package
Summary
MAL-2025-109235: Malicious code in subsequent_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 subsequent_beetle_0xrequest package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to automate the publication of derivative packages, often with randomized names, to inflate developer reputation scores. This behavior not only clutters the npm registry but also poses significant risks to developers who may unknowingly use these compromised packages.
Vulnerability Detail
The vulnerability stems from malicious code embedded within the subsequent_beetle_0xrequest package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which can lead to the proliferation of untrustworthy packages in the npm registry. The malicious payload is designed to continuously republish these variants, thereby polluting the ecosystem and potentially compromising the integrity of applications that rely on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall subsequent_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 temporary workaround, you can remove the subsequent_beetle_0xrequest package from your project by executing the following command: npm uninstall subsequent_beetle_0xrequest. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The subsequent_beetle_0xrequest package contains malicious code that poses a significant risk to developers and their applications. It is crucial to take immediate action by updating or removing the package to safeguard your projects. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.
See every vulnerability recorded for subsequent_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 introduction of malicious code into your application, potentially compromising its security and integrity.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. Visit Vulert Scanner to check your application without any signup.
Consider uninstalling the package as a temporary measure to mitigate the risk until a secure version is available.
Detailed information can be found in the vulnerability report on the GitHub repository for malicious packages.
