Which versions of bitu-user are malicious?

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

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

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

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

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

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

Malicious package

bitu-usernpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7224

Immediate action

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

npm uninstall bitu-user

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

5a21e27ba91483afc0fd82c98e3a15ddcdb343e40d84694f8cb6feaa6a83d48f

2fa84fdcf39b3d9eb92013f370512d40787949239d7bc5522ca5d7c4509ae642

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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