Which versions of aiuzubwjbsoj are malicious?

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

How do I remediate aiuzubwjbsoj if I installed it?

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

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

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

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

Malicious package

aiuzubwjbsojRubyGems

Advisory published Jul 7, 2026Updated Jul 23, 2026

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

MAL-2026-7501

Immediate action

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

gem uninstall aiuzubwjbsoj

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8220a368e1c1dbb515713765167deaf82e7fdf288dd98dd90a982e56fd4b5545

Detection & response playbook

Malicious package

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

Credits

ReversingLabs · finder

Detect & block this

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