Malicious Code Injection in long_peafowl_z3n Package
Summary
MAL-2025-105316: Malicious code in long_peafowl_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 long_peafowl_z3n package is part of the npm ecosystem and appears to be associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm registry.
Vulnerability Detail
The vulnerability in the long_peafowl_z3n package originates from its involvement in a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to pollution of the npm registry. This can result in developers unknowingly using compromised packages, which may lead to further security issues in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall long_peafowl_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 long_peafowl_z3n package from your project by executing the following command: npm uninstall long_peafowl_z3n. This will prevent any potential exploitation of the vulnerability until a fix is released.
Conclusion
The long_peafowl_z3n package contains a significant vulnerability that can compromise the security of applications using it. It is crucial to monitor for such vulnerabilities and take appropriate actions, such as updating or removing affected packages, to maintain the integrity of your software.
See every vulnerability recorded for long_peafowl_z3n →
FAQ
The long_peafowl_z3n package is an npm package associated with a token reward campaign that generates derivative packages to inflate developer reputation scores.
The vulnerability can lead to the use of compromised packages, which may introduce security risks and instability in your application.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
If you cannot update the package, it is advisable to remove it from your project to mitigate any potential risks.
