Malicious Code Injection in supposed_thrush_0xrequest Package
Summary
MAL-2025-109324: Malicious code in supposed_thrush_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 supposed_thrush_0xrequest package is part of a larger ecosystem that emerged during the tea.xyz token reward campaign. It is designed to facilitate various functionalities within the npm ecosystem. However, this package has been identified as malicious, containing scripts that manipulate package metadata and publish unauthorized derivatives, thereby compromising the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the package's malicious code, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to inflate developer reputation scores. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall supposed_thrush_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, avoid using the supposed_thrush_0xrequest package and monitor your project for any unauthorized changes. Regularly audit your package dependencies using tools like npm audit to identify and mitigate risks.
Conclusion
The supposed_thrush_0xrequest package poses significant risks due to its malicious code that alters package metadata and publishes unauthorized derivatives. It is crucial for developers to remove this package and monitor their dependencies to maintain the integrity of their projects. Utilizing tools like Vulert can aid in identifying and mitigating such vulnerabilities effectively.
See every vulnerability recorded for supposed_thrush_0xrequest →
FAQ
It is a package that has been identified as malicious, part of a campaign to inflate developer reputation scores through unauthorized publishing.
The vulnerability can lead to unauthorized changes in your project, potential security breaches, and pollution of the npm registry.
You should uninstall the package immediately using npm uninstall supposed_thrush_0xrequest and check for any other affected packages.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
