Which versions of biundleer are malicious?

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

How do I remediate biundleer if I installed it?

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

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

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

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

Malicious package

biundleerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in biundleer (RubyGems)

MAL-2026-16646

Immediate action

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

gem uninstall biundleer

Malicious versions

2 flagged

1.0.01.0.64011

Indicators of compromise (SHA-256)

521e8d52bffa0cb9bab9c4647995de79490069e443a64d6eef2e01fb2d616124

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07310

Credits

ReversingLabs · finder

Detect & block this

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