Which versions of biundlier are malicious?

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

How do I remediate biundlier if I installed it?

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

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

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

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

Malicious package

biundlierRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in biundlier (RubyGems)

MAL-2026-16670

Immediate action

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

gem uninstall biundlier

Malicious versions

2 flagged

1.0.01.0.97109

Indicators of compromise (SHA-256)

094e4711329b4e73da2bb12b20b9d236c176476129105adf7b2d94b7498ee40a

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07334

Credits

ReversingLabs · finder

Detect & block this

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