Malicious Code Injection in flat_peacock_z3n: A Threat to npm Users

flat_peacock_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94538: Malicious code in flat_peacock_z3n (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The package flat_peacock_z3n is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only clutters the npm registry but also poses a significant risk to users who may unknowingly install these compromised packages.

Vulnerability Detail

The vulnerability in flat_peacock_z3n originates from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This allows the package to continuously republish variants, polluting the npm registry and potentially leading to the installation of compromised software by unsuspecting developers. The malicious payload can also affect the integrity of projects that depend on this package, leading to 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 flat_peacock_z3n

If 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 flat_peacock_z3n package and replace it with a trusted alternative. Always verify the source and integrity of packages before installation.

Conclusion

The flat_peacock_z3n package poses a significant threat due to its malicious code designed to manipulate package metadata and pollute the npm registry. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for flat_peacock_z3n →

Share this vulnerability

FAQ

flat_peacock_z3n is an npm package that has been identified as malicious, designed to inflate developer reputation scores through automated publishing of derivative packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. Check your application against this vulnerability using the Vulert playground.

If you have installed flat_peacock_z3n, you should uninstall it immediately using the command: npm uninstall flat_peacock_z3n.

Yes, using npm packages can pose risks if the packages are not properly vetted. Malicious packages can compromise your application and lead to security vulnerabilities.

To prevent future vulnerabilities, regularly audit your dependencies, use trusted packages, and consider using tools like Vulert for real-time monitoring.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall flat_peacock_z3n

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback