Malicious Code Injection in rare_mandrill-silentdev Package

rare_mandrill-silentdev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107716: Malicious code in rare_mandrill-silentdev (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 rare_mandrill-silentdev 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 exploits npm's publishing capabilities, leading to potential security risks for developers and their applications.

Vulnerability Detail

The vulnerability in the rare_mandrill-silentdev package originates from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only compromises the integrity of the affected packages but also pollutes the npm registry, making it difficult for developers to trust the packages they use. The malicious payload can lead to unauthorized access, data breaches, and a compromised development environment.

How To Fix

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

npm uninstall rare_mandrill-silentdev

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 workaround, you can avoid using the rare_mandrill-silentdev package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities in real-time. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The rare_mandrill-silentdev package poses a significant security risk due to its malicious code injection. Developers should take immediate action to remove this package and monitor their applications for vulnerabilities. Utilizing tools like Vulert can enhance security by providing real-time alerts for open-source vulnerabilities.

See every vulnerability recorded for rare_mandrill-silentdev →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of derivative packages.

The vulnerability can lead to unauthorized modifications of your package.json file, potentially compromising your application's integrity and security.

You should uninstall the rare_mandrill-silentdev package immediately and monitor your project for any signs of compromise.

Yes, tools like Vulert can help monitor your application for open-source vulnerabilities in real-time using just your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall rare_mandrill-silentdev

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