Malicious Code Injection in colossal_camel_z3n: A Threat to npm Packages

colossal_camel_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93622: Malicious code in colossal_camel_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 colossal_camel_z3n is part of the npm ecosystem, which is widely used for JavaScript package management. This package is linked to the tea.xyz token reward campaign, notorious for flooding the npm registry with malicious packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with random names.

Vulnerability Detail

The vulnerability in colossal_camel_z3n stems from its inclusion in a campaign that employs autopublish scripts to modify package.json files. This manipulation removes private flags, alters version numbers, and generates random package names, leading to pollution of the npm registry. The malicious payload can compromise the integrity of the npm ecosystem, potentially affecting developers who unknowingly install these packages.

How To Fix

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

npm uninstall colossal_camel_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, you can avoid using the colossal_camel_z3n package and any packages that depend on it. Regularly audit your npm packages to ensure no malicious packages are present. You can also use the following command to check for vulnerabilities in your project: npm audit.

Conclusion

The colossal_camel_z3n package poses a significant risk due to its malicious code designed to manipulate npm packages. 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 colossal_camel_z3n →

Share this vulnerability

FAQ

colossal_camel_z3n is an npm package that has been identified as part of a malicious campaign targeting the npm registry.

The vulnerability can lead to the installation of malicious code that modifies your package.json file and pollutes the npm registry, potentially compromising your project's integrity.

You should uninstall the colossal_camel_z3n package immediately and check your package-lock.json for any references to it.

You can use tools like Vulert, which monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json.

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

How To Fix

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

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