Which versions of biundler-gem are malicious?

The following RubyGems versions of biundler-gem are flagged malicious: 1.0.56165. Treat any of these as compromised.

How do I remediate biundler-gem if I installed it?

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

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

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

Search your lockfiles and build artifacts for biundler-gem (version 1.0.56165).

Malicious package

biundler-gemRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

biundler-gem is a confirmed malicious RubyGems package (MAL-2026-16655) that executes malicious code on install (malicious version 1.0.56165). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in biundler-gem (RubyGems)

MAL-2026-16655

Immediate action

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

gem uninstall biundler-gem

Malicious versions

1 flagged

1.0.56165

Indicators of compromise (SHA-256)

85ba57da1b2dc901b8ea7c90ad241d4c79ef4a29aaa56d11f050f7cf9e440833

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07319

Credits

ReversingLabs · finder

Detect & block this

O3 blocks biundler-gem-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