Which versions of biuindler are malicious?

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

How do I remediate biuindler if I installed it?

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

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

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

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

Malicious package

biuindlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in biuindler (RubyGems)

MAL-2026-16621

Immediate action

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

gem uninstall biuindler

Malicious versions

2 flagged

1.0.01.0.36356

Indicators of compromise (SHA-256)

cfee0b8a48049faf3e86a2f49d78c713f3eae8724ca0f5fb35122d62a492bd51

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07285

Credits

ReversingLabs · finder

Detect & block this

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