Which versions of biundlelr are malicious?

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

How do I remediate biundlelr if I installed it?

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

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

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

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

Malicious package

biundlelrRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in biundlelr (RubyGems)

MAL-2026-16650

Immediate action

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

gem uninstall biundlelr

Malicious versions

2 flagged

1.0.01.0.91825

Indicators of compromise (SHA-256)

ddad86753c02f8eaf51d8bd92167cef382f05624989a90e7b3193e6b0936f1c4

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07314

Credits

ReversingLabs · finder

Detect & block this

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