Malicious Code Injection in mild_monkey_z3n Package - npm Vulnerability

mild_monkey_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95473: Malicious code in mild_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 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 mild_monkey_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and deployment of applications by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's publishing mechanisms, leading to potential security risks for developers and their applications.

Vulnerability Detail

The vulnerability in the mild_monkey_z3n package stems from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to modify the package.json file, removing private flags and changing version numbers. This behavior can lead to the unintentional exposure of sensitive information and the proliferation of malicious code within the npm ecosystem, ultimately compromising the integrity of applications that rely on these packages.

How To Fix

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

npm uninstall mild_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, avoid using the mild_monkey_z3n package and consider replacing it with an alternative package that provides similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.

Conclusion

The mild_monkey_z3n package poses a significant security risk due to its malicious code injection capabilities. It is crucial for developers to be vigilant and proactive in managing their dependencies, ensuring they are using secure and trusted packages. Regular monitoring and updates can help mitigate potential vulnerabilities.

See every vulnerability recorded for mild_monkey_z3n →

Share this vulnerability

FAQ

The mild_monkey_z3n package is an npm package used in JavaScript development, but it has been identified as part of a malicious campaign that compromises security.

This vulnerability can lead to the exposure of sensitive information and the introduction of malicious code into your application, potentially compromising its security.

If you have installed the mild_monkey_z3n package, you should uninstall it immediately and check for any other affected packages in your project.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can check your application using the Vulert playground without any signup.

Yes, consider using other reputable npm packages that provide similar functionality without the associated risks. Always research and verify the packages you choose.

How To Fix

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

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