Which versions of oaijx7497893 are malicious?

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

How do I remediate oaijx7497893 if I installed it?

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

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

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

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

Malicious package

oaijx7497893RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8270

Immediate action

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

gem uninstall oaijx7497893

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7e1397a905fd8d5d20fc3a873448d17dcedea56df5f7a54bf25b953aa114ca79

8463c2b0918de1113c03e6d96888f9e9c3d66e0f78e3f2243d623c27986e4144

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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