Which versions of biundlea are malicious?

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

How do I remediate biundlea if I installed it?

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

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

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

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

Malicious package

biundleaRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in biundlea (RubyGems)

MAL-2026-16642

Immediate action

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

gem uninstall biundlea

Malicious versions

2 flagged

1.0.01.0.71460

Indicators of compromise (SHA-256)

8b7c349d20094f307aebde3eb3f360dc1d5532d316473714e623ba7b170108da

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07306

Credits

ReversingLabs · finder

Detect & block this

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