Which versions of f0-email-verification are malicious?

The following npm versions of f0-email-verification are flagged malicious: 99.13.9, 99.31.9. Treat any of these as compromised.

How do I remediate f0-email-verification if I installed it?

Remove f0-email-verification 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 f0-email-verification — how do I know if it already compromised me?

If f0-email-verification 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 f0-email-verification part of a known attack campaign?

Yes — f0-email-verification is associated with the RLMA-2026-01944 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 f0-email-verification across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for f0-email-verification (2 malicious versions).

Malicious package

f0-email-verificationnpm

Advisory published Apr 16, 2026Updated Apr 23, 2026

f0-email-verification is a confirmed malicious npm package (MAL-2026-2760) that executes malicious code on install (malicious versions 99.13.9, 99.31.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in f0-email-verification (npm)

MAL-2026-2760

Immediate action

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

npm uninstall f0-email-verification

What this malware does

The package f0-email-verification was found to contain malicious code.

Malicious versions

2 flagged

99.13.999.31.9

Indicators of compromise (SHA-256)

5627215dfb489fa6892e458e3d37cd8880804e6a60dbf08f8b121bb66f3a0885

8f1be0fb20c0bda97570f04e023025da0e132b6f20c647025acbbaaad2916722

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for f0-email-verification (2 malicious versions).
If you installed it — respond
Remove f0-email-verification 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 f0-email-verification 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. f0-email-verification on npm has been identified as a malicious package (versions 99.13.9, 99.31.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01944

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks f0-email-verification-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