Which versions of bitu-sdk are malicious?

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

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

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

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

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

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

Malicious package

bitu-sdknpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7222

Immediate action

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

npm uninstall bitu-sdk

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

3b70fc220fb8cf95d3d653a645c7c650983db49aae3924646ce27b774e5b19e2

d1b8c6294919a933587a07bb8b084c3eff59d43e2e38ae99c8e0b7304a15e9bc

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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