Malicious Code Injection in possible_impala_z3n: A Threat to npm Packages
Summary
MAL-2025-107159: Malicious code in possible_impala_z3n (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 package 'possible_impala_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious activities aimed at inflating developer reputation scores. The package's functionality is compromised by the presence of scripts that automatically generate and publish derivative packages with randomized names, leading to potential pollution of the npm registry.
Vulnerability Detail
The vulnerability in 'possible_impala_z3n' originates from its association with malicious scripts designed to manipulate package metadata. These scripts remove private flags from package.json, alter version numbers, and generate random package names, which can lead to the proliferation of untrustworthy packages in the npm registry. This not only affects the integrity of the npm ecosystem but also poses risks to developers who may unknowingly depend on these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall possible_impala_z3nIf 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 remove the 'possible_impala_z3n' package from your project by executing the command: 'npm uninstall possible_impala_z3n'. This will prevent any malicious code from executing while you assess the situation.
Conclusion
The 'possible_impala_z3n' package is compromised by malicious scripts that threaten the integrity of the npm ecosystem. It is crucial for developers to take immediate action by updating or uninstalling the package to safeguard their applications. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.
See every vulnerability recorded for possible_impala_z3n →
FAQ
The malicious code modifies package.json files to remove private flags and generates random package names, which can lead to the pollution of the npm registry.
You can use Vulert, which monitors open-source vulnerabilities in your software by analyzing package-lock.json. Visit Vulert Scanner to check your application without any signup.
If an immediate update is not possible, consider uninstalling the package to mitigate risks until a secure version is available.
While specific exploits have not been detailed, the manipulation of package metadata poses a significant risk to the integrity of the npm ecosystem.
Regularly check for updates in your dependencies and utilize tools like Vulert to receive real-time alerts for open-source vulnerabilities.
