Which versions of biunrler are malicious?

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

How do I remediate biunrler if I installed it?

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

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

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

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

Malicious package

biunrlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in biunrler (RubyGems)

MAL-2026-16703

Immediate action

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

gem uninstall biunrler

Malicious versions

2 flagged

1.0.01.0.18829

Indicators of compromise (SHA-256)

65e569af6db4d215d1363d971a9e7e8e733051c8a3213de9a65b8e9f0545e2ef

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07367

Credits

ReversingLabs · finder

Detect & block this

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