Malicious Code Injection in multiple_mandrill_z3n Package

multiple_mandrill_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106001: Malicious code in multiple_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 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 multiple_mandrill_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts that manipulate package metadata and inflate developer reputation scores, posing a significant risk to developers and their projects.

Vulnerability Detail

The vulnerability in the multiple_mandrill_z3n package originates from its association with a malicious campaign that employs autopublish scripts. These scripts are designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of other packages. The ramifications include potential exposure of sensitive data and disruption of the development workflow.

How To Fix

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

npm uninstall multiple_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 multiple_mandrill_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your package-lock.json is monitored for any vulnerabilities using tools like Vulert.

Conclusion

The multiple_mandrill_z3n package contains malicious code that poses significant risks to developers and their projects. It is essential to remove this package and monitor your dependencies for vulnerabilities to maintain the integrity of your software.

See every vulnerability recorded for multiple_mandrill_z3n →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.

You can use Vulert to monitor your package-lock.json for vulnerabilities. Visit Vulert Scanner to check if your application is affected.

The risks include potential exposure of sensitive data, disruption of development processes, and the pollution of the npm registry with malicious packages.

Currently, there is no specific patch for the multiple_mandrill_z3n package. The recommended action is to uninstall the package.

Regularly monitor your dependencies using tools like Vulert, and stay updated on security advisories related to the packages you use.

How To Fix

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

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