Which versions of bitu-protocol are malicious?

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

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

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

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

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

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

Malicious package

bitu-protocolnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7221

Immediate action

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

npm uninstall bitu-protocol

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

43e52c70e23e07b74d3750c9c39c3c0b4646c697bfe4ee07cb6a8dea5f977f39

dc18dfe5db7ac1d9f8c37035c81dc2c2f702466508cbbb5da202f5b9232df571

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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