Which versions of biunidler are malicious?

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

How do I remediate biunidler if I installed it?

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

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

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

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

Malicious package

biunidlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in biunidler (RubyGems)

MAL-2026-16694

Immediate action

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

gem uninstall biunidler

Malicious versions

2 flagged

1.0.01.0.64010

Indicators of compromise (SHA-256)

284cdf2541636f3f0169f0e0a74a831a27ad2f6b84730f436cc547e474fc9afc

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07358

Credits

ReversingLabs · finder

Detect & block this

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