Which versions of oaiex8413575 are malicious?

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

How do I remediate oaiex8413575 if I installed it?

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

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

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

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

Malicious package

oaiex8413575RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8185

Immediate action

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

gem uninstall oaiex8413575

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

39e53f2b86fc40433d081a40a8d0179924991529068d9fc8ff914af8917e0a97

d3b935de23e816151b33e19009d1c4375a6e2a8b51d422cd44c2b2e9ca9195fd

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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