Malicious Code Injection in minor_mandrill_z3n: A Threat to npm Packages

minor_mandrill_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105869: Malicious code in minor_mandrill_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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The minor_mandrill_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 floods the npm registry with harmful packages, potentially compromising the integrity of applications that depend on it.

Vulnerability Detail

The vulnerability in minor_mandrill_z3n originates from its association with the tea.xyz token reward campaign, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious code modifies the package.json file by removing private flags, altering version numbers, and generating random package names, leading to pollution of the npm registry. This can result in developers inadvertently using compromised packages, exposing their applications to security risks and potential data breaches.

How To Fix

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

npm uninstall minor_mandrill_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 minor_mandrill_z3n package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages using tools like npm audit to identify and address vulnerabilities.

Conclusion

The minor_mandrill_z3n package poses a significant security risk due to its malicious code designed to manipulate npm registry packages. It is crucial for developers to remove this package from their projects and adopt best practices for monitoring and securing their applications against such vulnerabilities.

See every vulnerability recorded for minor_mandrill_z3n →

Share this vulnerability

FAQ

minor_mandrill_z3n is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of harmful packages.

If your application uses the minor_mandrill_z3n package, it may inadvertently include malicious code that can compromise security and lead to data breaches.

You should immediately uninstall the minor_mandrill_z3n package and check for any dependencies that may rely on it. Consider using alternative packages.

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.

Regularly audit your npm packages, keep them updated, and use security tools to monitor for vulnerabilities to minimize risks.

How To Fix

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

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