Malicious Code Injection in internal_worm_0xrequest Package
Summary
MAL-2025-104358: Malicious code in internal_worm_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 internal_worm_0xrequest package is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages with randomized names, primarily to inflate developer reputation scores for token rewards. This behavior poses significant risks to the integrity of the npm registry and the security of applications relying on these packages.
Vulnerability Detail
The vulnerability in the internal_worm_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 not only compromises the security of the affected applications but also pollutes the npm registry with numerous derivative packages, making it difficult for developers to find legitimate packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall internal_worm_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 prevent the installation of the internal_worm_0xrequest package by using npm's package-lock.json file to monitor dependencies. Ensure that your project does not include this package in its dependencies. You can also use the following command to uninstall it if it is already installed: npm uninstall internal_worm_0xrequest.
Conclusion
The internal_worm_0xrequest package poses a significant security risk due to its malicious behavior of modifying package files and flooding the npm registry. It is crucial for developers to remove this package from their projects and monitor their dependencies for any potential vulnerabilities.
See every vulnerability recorded for internal_worm_0xrequest →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to automate the publication of derivative packages.
The vulnerability can compromise your application's security by modifying critical files and polluting the npm registry with malicious packages.
Currently, there is no patched version available for the internal_worm_0xrequest package. The recommended action is to remove it.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.
