Which versions of aundlef are malicious?

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

How do I remediate aundlef if I installed it?

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

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

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

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

Malicious package

aundlefRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in aundlef (RubyGems)

MAL-2026-16556

Immediate action

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

gem uninstall aundlef

Malicious versions

2 flagged

1.0.01.0.88162

Indicators of compromise (SHA-256)

3c3c1d706efb54680e98a5c5a3191955b1c8d8d30d463818886355e448226457

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07157

Credits

ReversingLabs · finder

Detect & block this

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