Which versions of biunadler are malicious?

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

How do I remediate biunadler if I installed it?

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

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

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

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

Malicious package

biunadlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in biunadler (RubyGems)

MAL-2026-16625

Immediate action

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

gem uninstall biunadler

Malicious versions

2 flagged

1.0.01.0.77294

Indicators of compromise (SHA-256)

842d5adbf565c583df7614520ac96c4008bc96a0a5b4218a2f458f89b0606591

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07289

Credits

ReversingLabs · finder

Detect & block this

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