Which versions of ausndler are malicious?

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

How do I remediate ausndler if I installed it?

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

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

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

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

Malicious package

ausndlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in ausndler (RubyGems)

MAL-2026-16559

Immediate action

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

gem uninstall ausndler

Malicious versions

2 flagged

1.0.01.0.23323

Indicators of compromise (SHA-256)

78c4d223b5b746b39f9eeff8f9808bdad9361c5c3568b7c6a8780dbef00699d2

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07160

Credits

ReversingLabs · finder

Detect & block this

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