Malicious Code Injection in bitter_monkey_z3n Package - npm Vulnerability

bitter_monkey_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93390: Malicious code in bitter_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 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 bitter_monkey_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package was identified as part of a malicious campaign aimed at inflating developer reputation scores through the tea.xyz token reward system. It is designed to automatically generate and publish derivative packages with randomized names, which can lead to pollution of the npm registry and potential security risks for developers using these packages.

Vulnerability Detail

The vulnerability in the bitter_monkey_z3n package arises from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to create numerous derivative packages that clutter the npm registry, making it difficult for developers to find legitimate packages. The origin of this vulnerability is linked to a broader campaign that exploits npm's package publishing features, posing significant risks to the integrity of the npm ecosystem.

How To Fix

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

npm uninstall bitter_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 workaround, you can remove the bitter_monkey_z3n package from your project by executing the command: 'npm uninstall bitter_monkey_z3n'. This will prevent any malicious code from executing while you assess the impact of this vulnerability on your application.

Conclusion

The bitter_monkey_z3n package has been identified as a malicious entity within the npm ecosystem, capable of compromising the integrity of the registry and posing security risks to developers. It is crucial to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing vulnerability monitoring.

See every vulnerability recorded for bitter_monkey_z3n →

Share this vulnerability

FAQ

The bitter_monkey_z3n package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing of derivative packages.

This vulnerability can lead to the pollution of the npm registry, making it difficult to find legitimate packages and potentially exposing your application to security risks from malicious code.

If you have installed the bitter_monkey_z3n package, it is recommended to uninstall it immediately and check for any updates or patches that may address the vulnerability.

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

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

How To Fix

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

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