Malicious Code Injection in past_mandrill_0xrequest Package

past_mandrill_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106947: Malicious code in past_mandrill_0xrequest (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 past_mandrill_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate automated publishing of derivative packages, which can inflate developer reputation scores. However, it has been compromised to include malicious scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability in the past_mandrill_0xrequest package stems from its inclusion in a campaign that floods the npm registry with malicious packages. The malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior can lead to the pollution of the npm registry and can compromise the integrity of applications relying on this package.

How To Fix

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

npm uninstall past_mandrill_0xrequest

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 past_mandrill_0xrequest package and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The past_mandrill_0xrequest package has been identified as containing malicious code that can compromise application integrity. It is crucial to remove this package and monitor your projects for vulnerabilities using tools like Vulert to ensure ongoing security.

See every vulnerability recorded for past_mandrill_0xrequest →

Share this vulnerability

FAQ

It is an npm package that was part of a token reward campaign but has been compromised to include malicious code.

The malicious code can alter your package.json file, potentially leading to security vulnerabilities and the pollution of the npm registry.

You should remove the past_mandrill_0xrequest package from your project immediately and look for alternatives.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

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 past_mandrill_0xrequest

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