Malicious Code Injection in quickest_mandrill_z3n: A Threat to npm Users

quickest_mandrill_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-98893: Malicious code in quickest_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 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 quickest_mandrill_z3n package is part of the npm ecosystem, often utilized for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package, like others in the campaign, is designed to manipulate developer reputation scores through automated publishing scripts.

Vulnerability Detail

The vulnerability originates from the package being part of a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of control over their projects.

How To Fix

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

npm uninstall quickest_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 remove the quickest_mandrill_z3n package from your project by executing 'npm uninstall quickest_mandrill_z3n'. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The quickest_mandrill_z3n package poses a significant risk due to its malicious code that alters project files and inflates developer reputation scores. It is essential to take immediate action by updating or uninstalling the package and utilizing tools like Vulert for ongoing monitoring.

See every vulnerability recorded for quickest_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.

The vulnerability can lead to unauthorized modifications in your project, including changes to package.json and the introduction of potentially harmful code.

You should immediately uninstall the package and check your project for any unauthorized changes or vulnerabilities.

Yes, tools like Vulert can monitor your package-lock.json file to alert you in real-time for open-source vulnerabilities.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

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