Which versions of biunduer are malicious?

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

How do I remediate biunduer if I installed it?

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

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

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

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

Malicious package

biunduerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in biunduer (RubyGems)

MAL-2026-16690

Immediate action

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

gem uninstall biunduer

Malicious versions

2 flagged

1.0.01.0.79592

Indicators of compromise (SHA-256)

ddb6ec18232f9bc7a9b9bc1ff6a9208bd24dee08733c2809f30933bddf8146f3

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07354

Credits

ReversingLabs · finder

Detect & block this

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