Which versions of biundlero are malicious?

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

How do I remediate biundlero if I installed it?

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

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

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

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

Malicious package

biundleroRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in biundlero (RubyGems)

MAL-2026-16664

Immediate action

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

gem uninstall biundlero

Malicious versions

2 flagged

1.0.01.0.44201

Indicators of compromise (SHA-256)

483c79d0edd93ed44f0023bf21b13d6218a9ac45c1f89cef5f7e2c720c267dce

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07328

Credits

ReversingLabs · finder

Detect & block this

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