Which versions of mfaatest are malicious?

The following npm versions of mfaatest are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate mfaatest if I installed it?

Remove mfaatest from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

If mfaatest was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is mfaatest part of a known attack campaign?

Yes — mfaatest is associated with the IN-MAL-2026-019309 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 mfaatest across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for mfaatest (version 1.0.0).

Malicious package

mfaatestnpm

Advisory published Aug 31, 2026Updated Aug 31, 2026

mfaatest is a confirmed malicious npm package (MAL-2026-15629) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mfaatest (npm)

MAL-2026-15629

Immediate action

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

npm uninstall mfaatest

What this malware does

package.json declares dependency node-net-pool with its value set to an arbitrary HTTPS tarball URL (https://limbomail.com/api/attachment/fpwvxc__9DvM.Bjuueu1K2SkBC_KkgATls-oq05UsrNNY/pkg.tgz) rather than a registry version range. On npm install, npm fetches whatever bytes limbomail.com returns and installs them, executing any lifecycle scripts inside the fetched tarball. The source is unpinned, integrity-unchecked, and hosted on a domain unrelated to the package's stated publisher; the content can be swapped at any time by whoever controls that host. The package's own description claims 'zero runtime dependencies', contradicting the presence of this off-registry dependency and matching the smuggled-dropper shape.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

73e4ce261829117e316f9152160cdcb35c6ba66064f631baba1f8d528673b584

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for mfaatest (version 1.0.0).
If you installed it — respond
Remove mfaatest from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If mfaatest was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. mfaatest on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019309

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks mfaatest-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