Which versions of oaigx7857181 are malicious?

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

How do I remediate oaigx7857181 if I installed it?

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

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

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

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

Malicious package

oaigx7857181RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8213

Immediate action

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

gem uninstall oaigx7857181

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5d05128cff73213aaaffdee348fcccd4de62a4c2d843ca37aa05c53052c23e7a

4022d247d0b810ef10ba72cde71e0dd0e2e50d6c779760bf10887ccf56021055

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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