Which versions of oaijx5011813 are malicious?

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

How do I remediate oaijx5011813 if I installed it?

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

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

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

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

Malicious package

oaijx5011813RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8267

Immediate action

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

gem uninstall oaijx5011813

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

64d5f1045e7965f1de628a30ccac2b7fb9bbe8f5ace1fd21b4cc2a235b68414f

2aa417a4812506183dc311bf6dfc467375c7375c26af748e14968304ae3f474b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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