Which versions of mfafix are malicious?

The following npm versions of mfafix are flagged malicious: 1.1.0, 1.1.1. Treat any of these as compromised.

How do I remediate mfafix if I installed it?

mfafix is a typosquat — you almost certainly intended a legitimately-named package. Remove mfafix, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed mfafix — how do I know if it already compromised me?

If mfafix was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is mfafix part of a known attack campaign?

Yes — mfafix is associated with the IN-MAL-2026-019300, IN-MAL-2026-019310 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find mfafix across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for mfafix (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mfafix across your stack and pipelines.

Malicious package

mfafixnpm

mfafix is a confirmed malicious npm package (MAL-2026-15630) that typosquats a legitimate package to trick installs (malicious versions 1.1.0, 1.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mfafix (npm)

MAL-2026-15630

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall mfafix

What this malware does

lib/cache.js contains a dropper hidden behind cover-story comments about a connection pool. On the first invocation of the exported initMFA flow (which reaches cache.get() via _mfaStore.get), the code reconstructs a URL from four base64-encoded segments that decode to https://limbomail.com/api/attachment/..., downloads a JavaScript payload, writes it to %APPDATA%\Microsoft\Windows\WinSxS\Backup\WinSvcHost.js, and launches it under the host Node.js executable via child_process.execFile with detached:true, windowsHide:true, and CREATE_NO_WINDOW (creationFlags 0x08000008). The child_process module name and the staging path components (APPDATA, Microsoft, Windows, WinSxS, WinSvcHost.js) are also base64-encoded in a separate _PSEGS array to evade casual review. The destination host limbomail.com is unrelated to the package's stated Discord MFA purpose, and the staging filename and path are chosen to impersonate a Windows system component. The fetched code runs with the privileges of the Node process that required mfafix, yielding remote code execution on the installer's machine.

Malicious versions

2 flagged

1.1.01.1.1

Indicators of compromise (SHA-256)

4f10490485dfd11cdb9eeb6e29b104c0d70651d1d8853a339a7420a75d09d066

e7e4bbaa40c053e27518123a9eb7ac4239ff0f0891dd6e8e9ea85a2dff18cc23

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for mfafix (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mfafix across your stack and pipelines.
If you installed it — respond
mfafix is a typosquat — you almost certainly intended a legitimately-named package. Remove mfafix, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If mfafix was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks mfafix before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. mfafix on npm has been identified as a malicious package (versions 1.1.0, 1.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019300IN-MAL-2026-019310

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks mfafix-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database