Which versions of 511fola are malicious?

The following npm versions of 511fola are flagged malicious: 1.0.0, 99.99.99. Treat any of these as compromised.

How do I remediate 511fola if I installed it?

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

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

Yes — 511fola is associated with the RLMA-2026-01079, RLUA-2026-05954 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 511fola across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for 511fola (2 malicious versions).

Malicious package

511folanpm

Advisory published Jan 2, 2026Updated Sep 1, 2026

511fola is a confirmed malicious npm package (MAL-2026-9) that executes malicious code on install (malicious versions 1.0.0, 99.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in 511fola (npm)

MAL-2026-9

Immediate action

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

npm uninstall 511fola

What this malware does

The package 511fola was found to contain malicious code.

Malicious versions

2 flagged

1.0.099.99.99

Indicators of compromise (SHA-256)

0cb9d65067967eb3823731d9beecb461b0746c872d8ba438280cbfa55e572eb2

317e02ec5d989dc3c1e017cd5ba9bcb97f61f05b0f09c4ef0952d84a7ff28a37

9f88d0008a0babacf1179e04c5779ab51054fbf1bbd821791c5e8e90dc024787

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01079RLUA-2026-05954

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks 511fola-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