Malicious Code Injection in notable_chipmunk_z3n Package

notable_chipmunk_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-88870: Malicious code in notable_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 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 notable_chipmunk_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is suspected to be involved in a token reward campaign that has led to the proliferation of malicious packages on npm. It is designed to automate the generation and publication of derivative packages, which can compromise the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the notable_chipmunk_z3n package originates from its association with a malicious campaign that modifies package.json files to remove private flags, alters version numbers, and generates random package names. This behavior not only inflates developer reputation scores but also pollutes the npm registry with potentially harmful packages. The malicious payload can lead to unintentional installations of compromised packages, exposing users to security risks.

How To Fix

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

npm uninstall notable_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 remove the notable_chipmunk_z3n package from your project by executing: npm uninstall notable_chipmunk_z3n. This will prevent any potential exploitation of the vulnerability until a secure version is available.

Conclusion

The notable_chipmunk_z3n package has been identified as containing malicious code that can compromise the npm registry and potentially affect projects using it. It is crucial to update or remove the package to safeguard your applications from potential threats.

See every vulnerability recorded for notable_chipmunk_z3n →

Share this vulnerability

FAQ

It is an npm package that has been linked to a malicious campaign aimed at inflating developer reputation scores through the automatic generation 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.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file.

Absolutely! You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring any signup.

If immediate updates are not possible, consider removing the package as a temporary measure to mitigate risks until a secure version is available.

How To Fix

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

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