Which versions of biundlee are malicious?

The following RubyGems versions of biundlee are flagged malicious: 1.0.0, 1.0.60208. Treat any of these as compromised.

How do I remediate biundlee if I installed it?

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

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

Yes — biundlee is associated with the RLMA-2026-07309 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 biundlee across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for biundlee (2 malicious versions).

Malicious package

biundleeRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

biundlee is a confirmed malicious RubyGems package (MAL-2026-16645) that executes malicious code on install (malicious versions 1.0.0, 1.0.60208). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in biundlee (RubyGems)

MAL-2026-16645

Immediate action

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

gem uninstall biundlee

Malicious versions

2 flagged

1.0.01.0.60208

Indicators of compromise (SHA-256)

4c17db5fb7ce8e9c1e64a065c22f9107e231ce7424ad5946ac1964e9922659b6

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07309

Credits

ReversingLabs · finder

Detect & block this

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