Which versions of bliundler are malicious?

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

How do I remediate bliundler if I installed it?

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

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

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

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

Malicious package

bliundlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bliundler (RubyGems)

MAL-2026-16723

Immediate action

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

gem uninstall bliundler

Malicious versions

2 flagged

1.0.01.0.23197

Indicators of compromise (SHA-256)

0d7ccb526b553b01eefd3d4cf4e47a895817ea35ebf14b1552b6e39bf14ced4f

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07391

Credits

ReversingLabs · finder

Detect & block this

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