Which versions of express-flowlimit are malicious?

The following npm versions of express-flowlimit are flagged malicious: 2.2.7, 2.2.8, 2.2.9. Treat any of these as compromised.

How do I remediate express-flowlimit if I installed it?

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

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

Yes — express-flowlimit is associated with the RLMA-2026-05082, RLUA-2026-06233 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 express-flowlimit across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for express-flowlimit (3 malicious versions).

Malicious package

express-flowlimitnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

express-flowlimit is a confirmed malicious npm package (MAL-2026-7284) that executes malicious code on install (malicious versions 2.2.7, 2.2.8, 2.2.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in express-flowlimit (npm)

MAL-2026-7284

Immediate action

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

npm uninstall express-flowlimit

Malicious versions

3 flagged

2.2.72.2.82.2.9

Indicators of compromise (SHA-256)

9787663ed2da3d6fea1ae192bf96900ec0ffe38598d284f21e0ee763bdd6a8dc

00b00b1f786ecf21fb37a21f331a6800455e66dbae1bbcb55aacee82dd6a033b

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05082RLUA-2026-06233

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks express-flowlimit-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