Which versions of aunlder are malicious?

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

How do I remediate aunlder if I installed it?

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

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

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

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

Malicious package

aunlderRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in aunlder (RubyGems)

MAL-2026-16558

Immediate action

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

gem uninstall aunlder

Malicious versions

2 flagged

1.0.01.0.60483

Indicators of compromise (SHA-256)

904de988535fe0c9a5fec69fb7c0bde57619fb547e6d2393a4c8923bd9cf9e47

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07159

Credits

ReversingLabs · finder

Detect & block this

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