Malicious Code Injection in cool_baboon_z3n: A Threat to npm Packages

cool_baboon_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93810: Malicious code in cool_baboon_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

The package 'cool_baboon_z3n' is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards in the tea protocol, making it a significant concern for developers relying on npm for package management.

Vulnerability Detail

The vulnerability stems from malicious code embedded within the 'cool_baboon_z3n' package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential security risks for developers and their applications.

How To Fix

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

npm uninstall cool_baboon_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 'cool_baboon_z3n' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages using tools like Vulert to monitor for vulnerabilities.

Conclusion

The 'cool_baboon_z3n' package poses a significant risk due to its malicious code that manipulates the npm registry. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities using tools like Vulert. Staying informed and proactive is essential in maintaining the security of your applications.

See every vulnerability recorded for cool_baboon_z3n →

Share this vulnerability

FAQ

The 'cool_baboon_z3n' package is an npm package that has been identified as malicious, designed to manipulate the npm registry for token rewards.

The malicious code can alter your package.json, remove private flags, and republish variants, which can lead to security vulnerabilities and pollution of the npm registry.

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 have installed 'cool_baboon_z3n', you should uninstall it immediately using 'npm uninstall cool_baboon_z3n' and audit your project for any other malicious packages.

Yes, Vulert provides a service that monitors and alerts you in real-time for open-source vulnerabilities in your software using just your package-lock.json.

How To Fix

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

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