Which versions of bitu-core are malicious?

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

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

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

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

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

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

Malicious package

bitu-corenpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7220

Immediate action

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

npm uninstall bitu-core

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

d55287858e1f75e1a9de28e2766bd151a24f5332a9a8a9402d5fbbb7cdd949fd

b89a6950674941daa0772a76a4fcbf2b787557ebf967111ea0fcaa4ed03ca06f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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