Which versions of aiwhuleyftdv are malicious?

The following RubyGems versions of aiwhuleyftdv are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate aiwhuleyftdv if I installed it?

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

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

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

Search your lockfiles and build artifacts for aiwhuleyftdv (version 0.0.1).

Malicious package

aiwhuleyftdvRubyGems

Advisory published Jul 7, 2026Updated Jul 23, 2026

aiwhuleyftdv is a confirmed malicious RubyGems package (MAL-2026-7509) that executes malicious code on install (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in aiwhuleyftdv (RubyGems)

MAL-2026-7509

Immediate action

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

gem uninstall aiwhuleyftdv

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

74ba689c1a257648a61e98097bb7125b4c82884f2360770c978b233b2983b1cb

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02160

Credits

ReversingLabs · finder

Detect & block this

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