Malicious Code Injection in oral_mandrill_z3n: A Threat to npm Packages

oral_mandrill_z3n Updated 19 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-122410: Malicious code in oral_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 package 'oral_mandrill_z3n' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with malicious packages that contain scripts designed to manipulate package metadata and inflate developer reputation scores. The primary functionality of these packages is to automatically publish derivative versions with altered names and metadata, leading to potential abuse and pollution of the npm registry.

Vulnerability Detail

The vulnerability in 'oral_mandrill_z3n' originates from its association with malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, which can lead to the proliferation of unwanted packages in the npm registry. The ramifications include compromised developer reputations, potential security risks for applications relying on these packages, and a polluted npm ecosystem that makes it difficult to find legitimate packages.

How To Fix

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

npm uninstall oral_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 'oral_mandrill_z3n' and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use the following command to audit your npm packages for vulnerabilities: 'npm audit'.

Conclusion

The 'oral_mandrill_z3n' package poses a significant risk due to its malicious code designed to manipulate package metadata. It is essential to uninstall this package and monitor your projects for similar vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for oral_mandrill_z3n →

Share this vulnerability

FAQ

'oral_mandrill_z3n' is an npm package that has been identified as part of a malicious campaign to manipulate package metadata and inflate developer reputation scores.

This vulnerability can lead to the introduction of unwanted packages, potential security risks, and a polluted npm registry, which can affect the integrity of your application.

You should uninstall 'oral_mandrill_z3n' immediately using 'npm uninstall oral_mandrill_z3n' and monitor your project for any other vulnerable packages.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can also check your application for vulnerabilities using the Vulert playground.

To prevent future vulnerabilities, regularly audit your npm packages, keep them updated, and utilize tools like Vulert to monitor for any open-source vulnerabilities.

How To Fix

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

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