Which versions of fastnodemailer are malicious?

The following npm versions of fastnodemailer are flagged malicious: 8.0.2, 8.0.3, 8.0.4. Treat any of these as compromised.

How do I remediate fastnodemailer if I installed it?

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

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

Yes — fastnodemailer is associated with the GHSA-9w84-x6cf-c2vq, RLMA-2026-05088, RLUA-2026-06238 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 fastnodemailer across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for fastnodemailer (3 malicious versions).

Malicious package

fastnodemailernpm

Advisory published Jul 6, 2026Updated Sep 1, 2026

fastnodemailer is a confirmed malicious npm package (MAL-2026-6822) that executes malicious code on install (malicious versions 8.0.2, 8.0.3, 8.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in fastnodemailer (npm)

MAL-2026-6822

Immediate action

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

npm uninstall fastnodemailer

What this malware does

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

3 flagged

8.0.28.0.38.0.4

Indicators of compromise (SHA-256)

767201ea4bfd4f0c6950f9d6fadf4f9e38c9e72e56abd975ac1b49864ffc04a6

c961d50b149c953a85e3c33d68066039b4ae787cf7df584fcb900b8fa2860c70

285287b98e12d9c1e5272d922683350eeb19c2095d2116802fe8b802fcba9930

Detection & response playbook

Malicious package

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

Campaign

GHSA-9w84-x6cf-c2vqRLMA-2026-05088RLUA-2026-06238

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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