Which versions of blusndler are malicious?

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

How do I remediate blusndler if I installed it?

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

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

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

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

Malicious package

blusndlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in blusndler (RubyGems)

MAL-2026-16728

Immediate action

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

gem uninstall blusndler

Malicious versions

2 flagged

1.0.01.0.8984

Indicators of compromise (SHA-256)

b387949edae5b3a17949e4e853805f7122d92888a87553c2b11024b27e6090cd

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07396

Credits

ReversingLabs · finder

Detect & block this

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