Which versions of abusndler are malicious?

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

How do I remediate abusndler if I installed it?

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

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

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

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

Malicious package

abusndlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in abusndler (RubyGems)

MAL-2026-16552

Immediate action

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

gem uninstall abusndler

Malicious versions

2 flagged

1.0.01.0.26549

Indicators of compromise (SHA-256)

93549dd210188a283d2697090e71a4afdfa6228e9f5a11bdc0a08eb2a1f83eb9

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-06694

Credits

ReversingLabs · finder

Detect & block this

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