Which versions of biunler are malicious?

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

How do I remediate biunler if I installed it?

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

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

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

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

Malicious package

biunlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in biunler (RubyGems)

MAL-2026-16698

Immediate action

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

gem uninstall biunler

Malicious versions

2 flagged

1.0.01.0.49760

Indicators of compromise (SHA-256)

fe7eaebc6796db2b3c56f6cecb14d4e3a0fbd5a4c8cb1a229d47db2d71a22595

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07362

Credits

ReversingLabs · finder

Detect & block this

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