Which versions of aiuuwsosbsqp are malicious?

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

How do I remediate aiuuwsosbsqp if I installed it?

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

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

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

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

Malicious package

aiuuwsosbsqpRubyGems

Advisory published Jul 7, 2026Updated Jul 23, 2026

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

MAL-2026-7498

Immediate action

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

gem uninstall aiuuwsosbsqp

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c2edd058d14b0ae4858e9c4b8a87ff3edf5b50ce0d3e380cfd5475eaad4d654e

Detection & response playbook

Malicious package

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

Credits

ReversingLabs · finder

Detect & block this

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