Which versions of oaijx1603962 are malicious?

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

How do I remediate oaijx1603962 if I installed it?

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

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

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

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

Malicious package

oaijx1603962RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8264

Immediate action

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

gem uninstall oaijx1603962

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

79916c84fc2be6c7c477660429ef07ca1fec9c6e732d7829db6b3e9bc1652c62

f9d059f209ad3d34632e8a51ea0e395a0adddebbb820bc7115253575b59c7cf9

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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