Which versions of bundrix are malicious?

The following npm versions of bundrix are flagged malicious: 1.2.5. Treat any of these as compromised.

How do I remediate bundrix if I installed it?

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

If bundrix was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is bundrix part of a known attack campaign?

Yes — bundrix is associated with the GHSA-vrw9-m2mj-2fp9, RLMA-2026-04971, RLUA-2026-05503 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 bundrix across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bundrix (version 1.2.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bundrix across your stack and pipelines.

Malicious package

bundrixnpm

bundrix is a confirmed malicious npm package (MAL-2026-6658) that executes malicious code on install (malicious version 1.2.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bundrix (npm)

MAL-2026-6658

Immediate action

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

npm uninstall bundrix

What this malware does

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.2.5

Indicators of compromise (SHA-256)

f853223051c1cb68bc005b827209cb844bcde568473a9ff819fb34fccb042d74

6483548f09aca59d8ce186fcd313e2c86ab61719c5c1da2080b39c2061a94e0a

8d652a9512cacee1e13c7d0b6e025b04560bf7653901bd64b361278ae93b88af

e01c43c3dff37c5e6c29d4519ed86693e5b187eb5114e991ef60c02659f450a3

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bundrix (version 1.2.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bundrix across your stack and pipelines.
If you installed it — respond
Remove bundrix 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 bundrix was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks bundrix before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. bundrix on npm has been identified as a malicious package (version 1.2.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-vrw9-m2mj-2fp9RLMA-2026-04971RLUA-2026-05503

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks bundrix-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