Which versions of biunuler are malicious?

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

How do I remediate biunuler if I installed it?

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

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

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

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

Malicious package

biunulerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in biunuler (RubyGems)

MAL-2026-16706

Immediate action

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

gem uninstall biunuler

Malicious versions

2 flagged

1.0.01.0.34652

Indicators of compromise (SHA-256)

b1f8ca43fee20091291eddcab3eb5a3675766ab35f1b6988140268ae31fc4ca6

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07370

Credits

ReversingLabs · finder

Detect & block this

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