Which versions of biunsdler are malicious?

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

How do I remediate biunsdler if I installed it?

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

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

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

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

Malicious package

biunsdlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in biunsdler (RubyGems)

MAL-2026-16704

Immediate action

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

gem uninstall biunsdler

Malicious versions

2 flagged

1.0.01.0.63182

Indicators of compromise (SHA-256)

8d147d04f7b4baef2a7cd74570e49ec1cbb0ae962c787dd54964affe288238d9

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07368

Credits

ReversingLabs · finder

Detect & block this

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