Which versions of rn-bitu are malicious?

The following npm versions of rn-bitu are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate rn-bitu if I installed it?

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

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

Yes — rn-bitu is associated with the RLMA-2026-05294, RLUA-2026-06461 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 rn-bitu across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for rn-bitu (version 99.0.0).

Malicious package

rn-bitunpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

rn-bitu is a confirmed malicious npm package (MAL-2026-7401) that executes malicious code on install (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in rn-bitu (npm)

MAL-2026-7401

Immediate action

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

npm uninstall rn-bitu

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

22d980cc3996e4a01f7a0075e7ba64701da5588fa699b2c7a176bca0cf8b1349

680d7871359bbebb7061ed71971839894ad9cd1ae36fc6db847eafa699833f00

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05294RLUA-2026-06461

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks rn-bitu-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