Which versions of backoff-table are malicious?

The following npm versions of backoff-table are flagged malicious: 99.9.1. Treat any of these as compromised.

How do I remediate backoff-table if I installed it?

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

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

Yes — backoff-table is associated with the RLMA-2026-04955, RLUA-2026-06080 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 backoff-table across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for backoff-table (version 99.9.1).

Malicious package

backoff-tablenpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

backoff-table is a confirmed malicious npm package (MAL-2026-7217) that executes malicious code on install (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in backoff-table (npm)

MAL-2026-7217

Immediate action

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

npm uninstall backoff-table

Malicious versions

1 flagged

99.9.1

Indicators of compromise (SHA-256)

ef4b63210a17634e1f1bdbde2833b58fdff7bc12e62e0485f6d7e18d0a1df228

3d3126b281aeb3e709f3a13e4c1dc2139b8a76cc11765209f105120dac4c9394

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04955RLUA-2026-06080

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks backoff-table-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