Malicious Code Injection in jolly_buzzard_z3n Package

jolly_buzzard_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95139: Malicious code in jolly_buzzard_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 jolly_buzzard_z3n package is part of the npm ecosystem, typically used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to manipulate developer reputation scores through automated publishing scripts, making it a target for developers looking to maintain secure and reliable codebases.

Vulnerability Detail

The vulnerability in jolly_buzzard_z3n originates from its association with the tea.xyz token reward campaign, which employs autopublish scripts to generate and publish numerous derivative packages with randomized names. This malicious activity modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants, thereby polluting the npm registry. The ramifications include potential security risks for developers who unknowingly integrate this package into their projects, as it can lead to reputation damage and compromised code integrity.

How To Fix

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

npm uninstall jolly_buzzard_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 remove the jolly_buzzard_z3n package from your project by executing the following command: npm uninstall jolly_buzzard_z3n. This will prevent any malicious code from executing in your environment until a secure version is released.

Conclusion

The jolly_buzzard_z3n package poses a significant security risk due to its malicious code injection capabilities. It is crucial for developers to remain vigilant and take necessary actions, such as updating or removing the package, to safeguard their projects. Utilizing tools like Vulert can aid in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for jolly_buzzard_z3n →

Share this vulnerability

FAQ

jolly_buzzard_z3n is an npm package that has been identified as part of a malicious campaign to manipulate developer reputation scores.

The vulnerability can lead to the introduction of malicious code into your project, compromising its integrity and security.

You should uninstall the jolly_buzzard_z3n package immediately and monitor your project for any unusual behavior.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time using just your 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.

How To Fix

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

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