Which versions of oaifx2401408 are malicious?

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

How do I remediate oaifx2401408 if I installed it?

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

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

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

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

Malicious package

oaifx2401408RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8194

Immediate action

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

gem uninstall oaifx2401408

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d65739286d5e51389aec38e74f578f01f5b7f264773e7cf6cf04ffebd2b81bc7

6792c34f6b234e98effb9c34954087137f57a7e5eebb895ce4eeb17c3d7ca45d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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