Which versions of biundlet are malicious?

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

How do I remediate biundlet if I installed it?

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

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

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

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

Malicious package

biundletRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in biundlet (RubyGems)

MAL-2026-16668

Immediate action

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

gem uninstall biundlet

Malicious versions

2 flagged

1.0.01.0.63758

Indicators of compromise (SHA-256)

6426e5317841e28b987c0f744676c6d4e648f221a1b72c88054ac2db0641bcc5

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07332

Credits

ReversingLabs · finder

Detect & block this

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