Malicious Code Injection in bad_parrot_z3n: A Threat to npm Packages

bad_parrot_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99742: Malicious code in bad_parrot_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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

bad_parrot_z3n is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to manipulate package metadata, potentially affecting developers and users relying on it for legitimate purposes.

Vulnerability Detail

The vulnerability in bad_parrot_z3n stems from its inclusion in a series of malicious packages that utilize scripts to modify package.json files. These scripts remove private flags, alter version numbers, and generate random package names, leading to the pollution of the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which employs these tactics to exploit the npm ecosystem. The ramifications include compromised package integrity, potential security risks for applications using these packages, and a degraded developer reputation system.

How To Fix

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

npm uninstall bad_parrot_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 measure, avoid using the bad_parrot_z3n package and monitor your project for any dependencies that may have inadvertently included it. You can also use the following command to check for vulnerabilities in your project: npm audit.

Conclusion

The bad_parrot_z3n package poses a significant risk due to its malicious code designed to manipulate package metadata. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your applications.

See every vulnerability recorded for bad_parrot_z3n →

Share this vulnerability

FAQ

bad_parrot_z3n is an npm package identified as part of a malicious campaign that modifies package metadata to inflate developer reputation scores.

The vulnerability can lead to compromised package integrity, potential security risks, and pollution of the npm registry, affecting applications that rely on these packages.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.

You should uninstall the package immediately using the command: npm uninstall bad_parrot_z3n, and check for any dependencies that may have included it.

Yes, Vulert provides real-time monitoring for open-source vulnerabilities using just package-lock.json, allowing you to stay informed about potential threats.

How To Fix

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

npm uninstall bad_parrot_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