Which versions of biundlei are malicious?

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

How do I remediate biundlei if I installed it?

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

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

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

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

Malicious package

biundleiRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in biundlei (RubyGems)

MAL-2026-16648

Immediate action

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

gem uninstall biundlei

Malicious versions

2 flagged

1.0.01.0.36135

Indicators of compromise (SHA-256)

a2559d441b7602aba8710529f1e2089e9d397500ec03370fae30c7798351c2f3

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07312

Credits

ReversingLabs · finder

Detect & block this

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