Malicious Code Injection in organic_peacock_z3n: A Threat to npm Packages
Summary
MAL-2025-106781: Malicious code in organic_peacock_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 'organic_peacock_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 known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'organic_peacock_z3n' originates from its involvement in a malicious campaign that employs autopublish scripts to generate and publish derivative packages with randomized names. This manipulation alters the package.json file by removing private flags, changing version numbers, and continuously republishing variants, which can lead to pollution of the npm registry and compromise the security of dependent projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall organic_peacock_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 the 'organic_peacock_z3n' package and look for alternative packages that provide similar functionality without the associated risks. Ensure to review the package's reputation and security history before integrating it into your project.
Conclusion
The 'organic_peacock_z3n' package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain a secure development environment.
See every vulnerability recorded for organic_peacock_z3n →
FAQ
The vulnerability involves malicious code that modifies package metadata and repopulates the npm registry with harmful variants.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
You should uninstall the package immediately using 'npm uninstall organic_peacock_z3n' and review your project's dependencies for any other vulnerabilities.
Yes, consider searching the npm registry for similar packages that do not have a history of malicious activity.
Regularly audit your dependencies using tools like Vulert and stay informed about the security status of the packages you use.
