Malicious Code Injection in Successive Impala 0xRequest Package
Summary
MAL-2025-109263: Malicious code in successive_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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The 'successive_impala_0xrequest' package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which are often used to inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of applications that depend on it.
Vulnerability Detail
The vulnerability originates from the package's malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of these variants, polluting the npm registry and potentially affecting other developers and applications relying on this package. The malicious code can undermine the security of systems using this package, leading to reputational damage and operational risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall successive_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 workaround, you can prevent the installation of this malicious package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include 'successive_impala_0xrequest' in its dependencies. You can also utilize tools like Vulert to monitor for vulnerabilities in your project without requiring access to the code. For example, you can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner.
Conclusion
The 'successive_impala_0xrequest' package has been identified as containing malicious code that poses significant risks to applications using it. It is crucial to remove this package and monitor your dependencies for vulnerabilities to maintain the security and integrity of your software.
See every vulnerability recorded for successive_impala_0xrequest →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of derivative packages.
The malicious code can compromise the integrity of your application, leading to potential security risks and reputational damage.
You should remove the 'successive_impala_0xrequest' package and consider replacing it with a secure alternative.
Yes, you can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
