Malicious Code Vulnerability in mfasolver Package

mfasolver Updated 08 Oct 2026

Summary

08/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17663: Malicious code in mfasolver (npm). Affects mfasolver versions 1.0.0. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The mfasolver package is an npm library designed to assist with multi-factor authentication processes. It is intended for developers looking to integrate MFA solutions into their applications. However, this package has been found to contain a significant vulnerability that allows for the execution of malicious code, posing a serious risk to users and their applications.

Vulnerability Detail

The vulnerability originates from the mfasolver package's dependency on an off-registry HTTP source for its only runtime dependency, node-net-pool. This source points to a mutable GitHub repository, which means that the code fetched during installation can change at any time without notice. The absence of a commit pin and integrity hash allows an attacker to inject malicious code that will be executed upon installation. Additionally, the package disables certificate validation for TLS connections to discord.com, further exposing users to potential security risks.

How To Fix

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

npm uninstall mfasolver

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, avoid using the mfasolver package until a secure version is released. If you must use it, consider implementing strict network policies to limit its ability to make outbound connections, especially to untrusted sources.

Conclusion

The mfasolver package has a critical vulnerability that allows for the execution of malicious code due to its reliance on an untrusted dependency. It is essential for developers to take immediate action by updating the package or implementing workarounds to protect their applications. Regular monitoring for vulnerabilities using tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for mfasolver →

Share this vulnerability

FAQ

The mfasolver package is used for integrating multi-factor authentication solutions into applications.

The vulnerability allows for the execution of malicious code, which can compromise your application's security and data integrity.

Check the npm registry for updates to the mfasolver package. If a patched version is available, updating is recommended.

If you have installed the mfasolver package, immediately review your application for any suspicious activity and consider removing the package until it is updated.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check for vulnerabilities in your application using the Vulert playground without any signup.

How To Fix

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

npm uninstall mfasolver

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