Which versions of biundnler are malicious?

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

How do I remediate biundnler if I installed it?

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

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

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

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

Malicious package

biundnlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in biundnler (RubyGems)

MAL-2026-16684

Immediate action

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

gem uninstall biundnler

Malicious versions

2 flagged

1.0.01.0.47296

Indicators of compromise (SHA-256)

64b3274d98668be6ffd2af044702acc93acf5bc44d595cc083d4972e9ef6c794

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07348

Credits

ReversingLabs · finder

Detect & block this

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