Critical Malicious Code Vulnerability in 'mulle' Package

mulle Updated 02 Oct 2025

Summary

09/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5709: Malicious code in mulle (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 'mulle' package is an npm library that provides various functionalities for developers. It is widely used in JavaScript projects for its ease of integration and utility features. However, it has been identified to contain malicious code that compromises the security of any system where it is installed. This vulnerability poses a significant risk to users, as it can lead to unauthorized access and data breaches.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the 'mulle' package. This code can fully compromise any computer that has the package installed, allowing attackers to gain control over the system. The ramifications include potential theft of sensitive information, unauthorized access to files, and the installation of additional malicious software. Users are advised to treat any system with this package as compromised and take immediate action to secure their data.

How To Fix

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

npm uninstall mulle

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, if you cannot immediately remove the package, consider isolating the environment where 'mulle' is used. This can be done by using containerization tools like Docker to limit the exposure of your main system. However, this is not a permanent solution, and removing the package is strongly recommended.

Conclusion

The 'mulle' package has been identified as containing malicious code that poses a significant risk to users. Immediate action is required to remove the package and secure any affected systems. Utilizing tools like Vulert can help in monitoring for vulnerabilities in the future.

See every vulnerability recorded for mulle →

Share this vulnerability

FAQ

Immediately uninstall the package using 'npm uninstall mulle' and assess your system for any signs of compromise.

You can use Vulert to monitor and alert for open-source vulnerabilities. Visit Vulert Scanner to check your application without any signup.

Keeping the 'mulle' package can lead to unauthorized access to your system, data breaches, and potential installation of further malicious software.

Currently, there is no patch available. The best course of action is to remove the package entirely.

Vulert uses the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities, ensuring your software remains secure.

How To Fix

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

npm uninstall mulle

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