Which versions of aiwmirzlwefr are malicious?

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

How do I remediate aiwmirzlwefr if I installed it?

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

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

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

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

Malicious package

aiwmirzlwefrRubyGems

Advisory published Jul 7, 2026Updated Jul 23, 2026

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

MAL-2026-7514

Immediate action

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

gem uninstall aiwmirzlwefr

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a529989fe2c70965857fc0e98486b719f7da0f12e369c963f77c8edb41d1fc04

Detection & response playbook

Malicious package

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

Credits

ReversingLabs · finder

Detect & block this

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