Which versions of biundlerl are malicious?

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

How do I remediate biundlerl if I installed it?

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

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

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

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

Malicious package

biundlerlRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in biundlerl (RubyGems)

MAL-2026-16662

Immediate action

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

gem uninstall biundlerl

Malicious versions

2 flagged

1.0.01.0.92299

Indicators of compromise (SHA-256)

c6f1a35abaf237328801bfd10edf28336970009c80deb23e7dc8ad175d73daab

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07326

Credits

ReversingLabs · finder

Detect & block this

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