Which versions of oaijx3058720 are malicious?

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

How do I remediate oaijx3058720 if I installed it?

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

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

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

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

Malicious package

oaijx3058720RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8266

Immediate action

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

gem uninstall oaijx3058720

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d489128513f35dfc6fadd2ec07d04cf1e6debeb8ff842e29b8604ebbf703b691

74ec58ea01d50e268d1340341cc0db2eb5cf543e6408596ea4d8d474a77cd1a7

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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