Malicious Code Injection in strong_pheasant_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-109207: Malicious code in strong_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 package 'strong_pheasant_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the generation of derivative packages with randomized names.
Vulnerability Detail
The vulnerability in 'strong_pheasant_z3n' originates from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to modify the package.json file by removing private flags, altering version numbers, and generating random names. 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 strong_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 avoid using 'strong_pheasant_z3n' and any packages that depend on it. Regularly audit your package-lock.json file for any suspicious packages and remove them as necessary.
Conclusion
The 'strong_pheasant_z3n' package poses a significant risk due to its malicious behavior aimed at manipulating the npm registry. It is essential for developers to be vigilant and remove any instances of this package from their projects to maintain the integrity of their applications and the npm ecosystem.
See every vulnerability recorded for strong_pheasant_z3n →
FAQ
'strong_pheasant_z3n' is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.
The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.
You should uninstall 'strong_pheasant_z3n' immediately and check your project for any other compromised packages.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
