Malicious Code Vulnerability in troubled_impala_0xrequest Package
Summary
MAL-2025-109851: Malicious code in troubled_impala_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 troubled_impala_0xrequest package is part of the npm ecosystem, often used in JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. This package, like others in the campaign, is designed to manipulate npm's publishing system, potentially affecting developers' reputations and 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, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores for token rewards, leading to the continuous republishing of variants that pollute the npm registry. The ramifications include compromised package integrity, potential security risks for applications using the package, and a degraded developer experience within the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall troubled_impala_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 avoid using the troubled_impala_0xrequest package until a fix is released. Additionally, you can monitor your package-lock.json file for any changes that may indicate the presence of this malicious package.
Conclusion
The troubled_impala_0xrequest package contains a significant vulnerability that can affect the integrity of applications using it. It is crucial to take immediate action by updating or removing the package and to utilize monitoring tools like Vulert to stay informed about potential vulnerabilities in your dependencies.
See every vulnerability recorded for troubled_impala_0xrequest →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, known for containing malicious code.
The vulnerability can compromise the integrity of your application by introducing malicious code that alters package metadata and inflates developer reputation scores.
You should update the package to a patched version or remove it from your project to mitigate the risk.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.
Regularly audit your dependencies, keep them updated, and use tools like Vulert to monitor for vulnerabilities in your open-source packages.
