Which versions of biundlera are malicious?

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

How do I remediate biundlera if I installed it?

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

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

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

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

Malicious package

biundleraRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in biundlera (RubyGems)

MAL-2026-16659

Immediate action

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

gem uninstall biundlera

Malicious versions

2 flagged

1.0.01.0.54273

Indicators of compromise (SHA-256)

cf399a5c936338bf4669d933046dd1eb5c7e2e0ab2704f11a7c0297cac9c163c

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07323

Credits

ReversingLabs · finder

Detect & block this

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