Which versions of rn-bitu-user are malicious?

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

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

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

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

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

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

Malicious package

rn-bitu-usernpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

rn-bitu-user is a confirmed malicious npm package (MAL-2026-7402) 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-user (npm)

MAL-2026-7402

Immediate action

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

npm uninstall rn-bitu-user

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

17be1210bc2c9a53daf7e017f4e1968216f425324d3286237fc58004e5670b7c

b4e7fb92a57141548eddce86f6027c983967e89416b301ef6754a337ee56d02e

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for rn-bitu-user (version 99.0.0).
If you installed it — respond
Remove rn-bitu-user 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-user 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-user 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-05295RLUA-2026-06462

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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