Malicious Code Injection in future_pheasant_z3n Package
Summary
MAL-2025-103000: Malicious code in future_pheasant_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 future_pheasant_z3n package is part of the npm ecosystem, often used in JavaScript applications. It appears to be associated with the tea.xyz token reward campaign, which has been linked to a series of malicious packages that flood the npm registry. These packages are designed to inflate developer reputation scores through automated publishing scripts.
Vulnerability Detail
The vulnerability in the future_pheasant_z3n package stems from its malicious payload that modifies the package.json file. This includes removing private flags, altering version numbers, and generating random package names to continuously republish variants. This behavior not only pollutes the npm registry but also compromises the integrity of applications that depend on this package, potentially leading to security breaches and loss of developer trust.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall future_pheasant_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 future_pheasant_z3n package from your project by using the command: npm uninstall future_pheasant_z3n. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The future_pheasant_z3n package contains a serious vulnerability that can compromise applications relying on it. It is crucial to take immediate action by updating or removing the package to ensure the security of your software. Utilizing tools like Vulert can help monitor and alert you to such vulnerabilities in real-time.
See every vulnerability recorded for future_pheasant_z3n →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.
The vulnerability can lead to unauthorized modifications of your package.json file, potentially compromising your application's integrity.
You should immediately update or uninstall the package to mitigate any risks associated with the vulnerability.
Yes, you can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.
You can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without signing up.
