Which versions of bitu-trade are malicious?

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

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

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

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

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

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

Malicious package

bitu-tradenpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7223

Immediate action

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

npm uninstall bitu-trade

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

b1423e3ba9b4eed8e6407ceae436e814c093470043203afef4e50cc23d28eff1

1a53dc9c12eb499f6c3a41a5a932f41b09c73fbd51d93ffe9d03c55dad25819a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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