Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

rate-limits-flexiblenpm

rate-limits-flexible is a confirmed malicious npm package (MAL-2026-5627) that executes malicious code on install (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in rate-limits-flexible (npm)

MAL-2026-5627
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall rate-limits-flexible

What this malware does

The package was found to contain malicious code or consuming dependency that contains malicious code

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

1 flagged
1.0.1

Indicators of compromise (SHA-256)

f51c182413a9d071e2e2109f7477ff0fb1b05fae4e5e98a46bb53e7d8b2d693b
809e7f8796ee45bb12d644bd48e71cbfca430e22d40b06ea0e0437097d131068

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for rate-limits-flexible (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rate-limits-flexible across your stack and pipelines.

  2. If you installed it — respond

    Remove rate-limits-flexible 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.

  3. Did it already run?

    If rate-limits-flexible was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks rate-limits-flexible before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

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

Campaign

GHSA-hg8j-2wmv-w4v6IN-MAL-2026-009475

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks rate-limits-flexible-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.

Explore

rate-limits-flexible (npm) malicious package — MAL-2026-5627 | O3 Security