Malicious Code Injection in Colourful Baboon Z3N Package

colourful_baboon_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100692: Malicious code in colourful_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 Colourful Baboon Z3N package is a part of the npm ecosystem, often utilized in various JavaScript applications. It is designed to facilitate the integration of functionalities within projects. However, this package has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to potential security risks for developers and users alike.

Vulnerability Detail

The vulnerability in the Colourful Baboon Z3N package stems from its association with the tea.xyz token reward campaign. This campaign has flooded the npm registry with packages that contain malicious scripts designed to manipulate package metadata. Specifically, the malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only inflates developer reputation scores but also pollutes the npm registry, making it difficult for users to identify legitimate packages. The ramifications include potential exposure to further malicious activities and the degradation 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 colourful_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 Colourful Baboon Z3N package and look for alternative packages that provide similar functionalities without the associated risks. Additionally, you can monitor your project's dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time based on your package-lock.json file.

Conclusion

The Colourful Baboon Z3N package poses a significant security risk due to its malicious code injection capabilities. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications by providing real-time alerts for open-source vulnerabilities.

See every vulnerability recorded for colourful_baboon_z3n →

Share this vulnerability

FAQ

Colourful Baboon Z3N is an npm package used in JavaScript applications, but it has been identified as part of a malicious campaign that exploits npm's publishing system.

The vulnerability can lead to the injection of malicious code, which may compromise your application's integrity and expose it to further attacks.

You should remove the Colourful Baboon Z3N package from your project and monitor for any updates or patches that may address the vulnerability.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Regularly monitor your dependencies using tools like Vulert, keep your packages updated, and review security advisories related to the packages you use.

How To Fix

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

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