Which versions of basndler are malicious?

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

How do I remediate basndler if I installed it?

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

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

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

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

Malicious package

basndlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in basndler (RubyGems)

MAL-2026-16565

Immediate action

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

gem uninstall basndler

Malicious versions

2 flagged

1.0.01.0.53497

Indicators of compromise (SHA-256)

d0b75ca0b1034a1f45024dc1612d59cea69e8cac9f13e55e0a3edf754d595151

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07197

Credits

ReversingLabs · finder

Detect & block this

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