Which versions of aizzofpvqxbu are malicious?

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

How do I remediate aizzofpvqxbu if I installed it?

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

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

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

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

Malicious package

aizzofpvqxbuRubyGems

Advisory published Jul 7, 2026Updated Jul 23, 2026

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

MAL-2026-7540

Immediate action

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

gem uninstall aizzofpvqxbu

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

db09a5948a4e3e7dcfe916ad356e2fc2f27d61b336799b5349b1eda8ba97cb79

Detection & response playbook

Malicious package

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

Credits

ReversingLabs · finder

Detect & block this

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