Which versions of bitopro-trade-guard are malicious?

The following npm versions of bitopro-trade-guard are flagged malicious: 1.1.0. Treat any of these as compromised.

How do I remediate bitopro-trade-guard if I installed it?

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

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

Yes — bitopro-trade-guard is associated with the RLMA-2026-04958, RLUA-2026-06087 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 bitopro-trade-guard across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for bitopro-trade-guard (version 1.1.0).

Malicious package

bitopro-trade-guardnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

bitopro-trade-guard is a confirmed malicious npm package (MAL-2026-7218) that executes malicious code on install (malicious version 1.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bitopro-trade-guard (npm)

MAL-2026-7218

Immediate action

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

npm uninstall bitopro-trade-guard

Malicious versions

1 flagged

1.1.0

Indicators of compromise (SHA-256)

582f133fdc29c850bc135b4a000e87efa70ad58dd1995198b254be21e2fa4b48

cde9ab41cf10ef0f3394440d74a6a8f1ec5dece9a0fa6a5df6766d86075ad7c3

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for bitopro-trade-guard (version 1.1.0).
If you installed it — respond
Remove bitopro-trade-guard 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 bitopro-trade-guard 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. bitopro-trade-guard on npm has been identified as a malicious package (version 1.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-04958RLUA-2026-06087

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks bitopro-trade-guard-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