Which versions of aizjmmmwsreb are malicious?

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

How do I remediate aizjmmmwsreb if I installed it?

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

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

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

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

Malicious package

aizjmmmwsrebRubyGems

Advisory published Jul 7, 2026Updated Jul 23, 2026

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

MAL-2026-7534

Immediate action

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

gem uninstall aizjmmmwsreb

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c0d67cb7cd833462b66d990e226b912ca2705981c5c4a91b5026310b71c1489b

Detection & response playbook

Malicious package

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

Credits

ReversingLabs · finder

Detect & block this

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