Critical Malicious Code Vulnerability in m-backdoor Package

m-backdoor Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-25734: Malicious code in m-backdoor (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 m-backdoor package is an npm library that is designed to provide various functionalities for developers. However, it has been identified to contain malicious code that poses significant security risks to applications that utilize it. This vulnerability can lead to unauthorized access, data breaches, and other malicious activities.

Vulnerability Detail

The vulnerability in the m-backdoor package originates from the inclusion of malicious code that can execute harmful actions on the host system. This code can compromise the integrity of applications, allowing attackers to gain unauthorized access to sensitive data and potentially control the affected systems. The malicious nature of this vulnerability makes it critical for developers to address it immediately.

How To Fix

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

npm uninstall m-backdoor

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

If you cannot update the package immediately, consider removing the m-backdoor package from your project and replacing it with a secure alternative. You can do this by executing: npm uninstall m-backdoor.

Conclusion

The m-backdoor package contains a critical vulnerability due to malicious code that can severely impact applications. It is crucial for developers to update or remove this package to safeguard their systems and data.

See every vulnerability recorded for m-backdoor →

Share this vulnerability

FAQ

The m-backdoor package is an npm library that provides various functionalities but has been found to contain malicious code.

The malicious code can lead to unauthorized access, data breaches, and control over the affected systems, posing significant security risks.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.

If you cannot update the package, consider removing it from your project and replacing it with a secure alternative.

More information can be found on the GitHub repository of the malicious package, which details the vulnerability and its implications.

Related vulnerabilities

Recent vulnerabilities recorded for m-backdoor.

How To Fix

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

npm uninstall m-backdoor

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