Which versions of aiwhwinedxvy are malicious?

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

How do I remediate aiwhwinedxvy if I installed it?

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

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

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

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

Malicious package

aiwhwinedxvyRubyGems

Advisory published Jul 7, 2026Updated Jul 23, 2026

aiwhwinedxvy is a confirmed malicious RubyGems package (MAL-2026-7510) 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 aiwhwinedxvy (RubyGems)

MAL-2026-7510

Immediate action

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

gem uninstall aiwhwinedxvy

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d23f8a2b48e87d15aec2004bf5ffe3c5a909586d64ac3dc4c68e9f91dea89323

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for aiwhwinedxvy (version 0.0.1).
If you installed it — respond
Remove aiwhwinedxvy 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 aiwhwinedxvy 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. aiwhwinedxvy 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-02161

Credits

ReversingLabs · finder

Detect & block this

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