Which versions of biundaer are malicious?

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

How do I remediate biundaer if I installed it?

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

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

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

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

Malicious package

biundaerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in biundaer (RubyGems)

MAL-2026-16628

Immediate action

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

gem uninstall biundaer

Malicious versions

2 flagged

1.0.01.0.9461

Indicators of compromise (SHA-256)

64696da2a6d26a0f9db31c552ee7b021fe7119d494663d8c89ea152cf6f308cb

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07292

Credits

ReversingLabs · finder

Detect & block this

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