Malicious Code Injection in dull_monkey_z3n: A Threat to npm Packages

dull_monkey_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94134: Malicious code in dull_monkey_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 Your last release was probably never penetration tested 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 'dull_monkey_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized by developers to manage dependencies in their projects. However, this package has been identified as part of a malicious campaign that seeks to exploit npm's publishing capabilities, leading to potential security risks for users.

Vulnerability Detail

The vulnerability in 'dull_monkey_z3n' originates from its association with the tea.xyz token reward campaign. This campaign has led to the creation of numerous packages that contain scripts designed to automatically publish derivative packages with randomized names. These scripts modify the package.json file to remove private flags, alter version numbers, and generate random package names, ultimately polluting the npm registry. The ramifications include compromised developer reputation scores and potential security risks for applications relying on these packages.

How To Fix

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

npm uninstall dull_monkey_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 'dull_monkey_z3n' package and replace it with a trusted alternative. Always verify the integrity of packages before including them in your project.

Conclusion

The 'dull_monkey_z3n' package poses a significant security risk due to its malicious code designed to manipulate npm package metadata. It is essential for developers to remove this package and monitor their projects for similar vulnerabilities. Utilizing tools like Vulert can help ensure the security of your applications.

See every vulnerability recorded for dull_monkey_z3n →

Share this vulnerability

FAQ

The main issue is that it contains malicious code designed to manipulate package metadata and flood the npm registry with derivative packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

You should uninstall the package immediately using 'npm uninstall dull_monkey_z3n' and review your dependencies for any other malicious packages.

Yes, using this package can lead to security vulnerabilities in your application, as it may introduce malicious code that compromises your project's integrity.

Regularly audit your dependencies, use tools like Vulert for monitoring, and only install packages from trusted sources.

How To Fix

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

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