Which versions of bode-which are malicious?

The following npm versions of bode-which are flagged malicious: 1.1.2, 1.1.4, 8.7.6. Treat any of these as compromised.

How do I remediate bode-which if I installed it?

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

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

Yes — bode-which is associated with the RLMA-2026-04967, RLUA-2026-06096 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 bode-which across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for bode-which (3 malicious versions).

Malicious package

bode-whichnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

bode-which is a confirmed malicious npm package (MAL-2026-7227) that executes malicious code on install (malicious versions 1.1.2, 1.1.4, 8.7.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bode-which (npm)

MAL-2026-7227

Immediate action

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

npm uninstall bode-which

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

8aaa646ad3ded52d3e2b1bbf7c17dc05e7f384951fa225589d4afc4086290bc4

e949371f9cd434d52055a897f3a40e39cc9e03ca02d7514aeab888b04fb9c030

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for bode-which (3 malicious versions).
If you installed it — respond
Remove bode-which 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 bode-which 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. bode-which on npm has been identified as a malicious package (versions 1.1.2, 1.1.4, 8.7.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-04967RLUA-2026-06096

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks bode-which-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