Which versions of oaijx7803530 are malicious?

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

How do I remediate oaijx7803530 if I installed it?

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

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

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

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

Malicious package

oaijx7803530RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8272

Immediate action

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

gem uninstall oaijx7803530

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

42d1b5042ad66966ba4cd36cc2309bfa8738c0d6d917403c36bda1765f76f7b2

74d59c67999121b8ee83a8c536fda29558af46508ded95c09d05899ff209160e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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