Which versions of bundleliep are malicious?

The following npm versions of bundleliep are flagged malicious: 21.22.1. Treat any of these as compromised.

How do I remediate bundleliep if I installed it?

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

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

Yes — bundleliep is associated with the GHSA-cgv6-3q9c-8x8c, RLMA-2025-04935, RLUA-2026-01135 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 bundleliep 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 bundleliep (version 21.22.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bundleliep across your stack and pipelines.

Malicious package

bundleliepnpm

bundleliep is a confirmed malicious npm package (MAL-2025-47053) that executes malicious code on install (malicious version 21.22.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bundleliep (npm)

MAL-2025-47053

Immediate action

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

npm uninstall bundleliep

What this malware does

The package bundleliep was found to contain malicious code.

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

21.22.1

Indicators of compromise (SHA-256)

340754ac2fb58c38b60047b573870d36d4e8ffae96845c4da4f96b2ac8a43d91

8a356a3f82cce2ffe193cbaad468bac08e799eb53d01ad0444ff8d36b2802635

1a045ddc1487939ffb50aa428f22f344e8a21e29afc1350b902167f23d4c0508

0eec9128367c1e6feb8e1bb88d3ce3eab1b4b8358cfb1dd7d033f06f8f9ab455

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 bundleliep (version 21.22.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bundleliep across your stack and pipelines.
If you installed it — respond
Remove bundleliep 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 bundleliep 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 bundleliep 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. bundleliep on npm has been identified as a malicious package (version 21.22.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-cgv6-3q9c-8x8cRLMA-2025-04935RLUA-2026-01135

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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