Malicious Code Injection in determined_termite_0xrequest Package
Summary
MAL-2025-101382: Malicious code in determined_termite_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 determined_termite_0xrequest package is part of the npm ecosystem, primarily used for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood npm with numerous packages. This package, like others in the campaign, is designed to manipulate npm's registry and developer reputation scores through automated scripts.
Vulnerability Detail
The vulnerability in the determined_termite_0xrequest package originates from its malicious design, which includes scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of applications that depend on this package. The malicious payload can inflate developer reputation scores fraudulently, posing a risk to the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall determined_termite_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 malicious package by using npm's package-lock.json file to lock your dependencies. Additionally, consider using a tool like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without requiring any signup.
Conclusion
The determined_termite_0xrequest package poses a significant risk due to its malicious code designed to manipulate npm's registry. It is crucial to remove this package from your projects and monitor for any vulnerabilities using tools like Vulert to ensure the security of your applications.
See every vulnerability recorded for determined_termite_0xrequest →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, known for flooding the npm registry with malicious packages.
The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your application by introducing malicious code.
You should uninstall the determined_termite_0xrequest package immediately and check your package-lock.json for any references to it.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
