Malicious Code Injection in warm_chipmunk_z3n: A Threat to npm Packages

warm_chipmunk_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97312: Malicious code in warm_chipmunk_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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package warm_chipmunk_z3n is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with packages that contain scripts designed to manipulate package metadata. The primary function of these packages is to inflate developer reputation scores for token rewards, which can lead to a polluted npm registry and potential security risks for users.

Vulnerability Detail

The vulnerability in warm_chipmunk_z3n stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, which can lead to the continuous republishing of these variants. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which employs autopublish scripts to automate the creation of derivative packages. The ramifications include the potential for developers to unknowingly install compromised packages, leading to security breaches and loss 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 warm_chipmunk_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 warm_chipmunk_z3n package altogether and monitor your dependencies for any malicious activity. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.

Conclusion

The warm_chipmunk_z3n package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with compromised packages. It is crucial to remove this package from your projects and utilize tools like Vulert for ongoing monitoring to safeguard your applications.

See every vulnerability recorded for warm_chipmunk_z3n →

Share this vulnerability

FAQ

warm_chipmunk_z3n is an npm package that is part of a malicious campaign to inflate developer reputation scores through the creation of derivative packages.

The vulnerability can lead to the installation of compromised packages, which may introduce security risks and affect the integrity of your project.

If you have installed warm_chipmunk_z3n, it is recommended to uninstall it immediately and monitor your project for any unusual activity.

Yes, you can prevent such vulnerabilities by regularly auditing your dependencies, using tools like Vulert to monitor for vulnerabilities, and being cautious when adding new packages.

Vulert is a tool that monitors your package-lock.json for open-source vulnerabilities in real-time. You can use the Vulert playground 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 warm_chipmunk_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