Which versions of oaifx9667097 are malicious?

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

How do I remediate oaifx9667097 if I installed it?

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

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

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

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

Malicious package

oaifx9667097RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8205

Immediate action

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

gem uninstall oaifx9667097

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8364d13dd526bceed41c811bea820d9308d7181a773f0e33fdcc58ba078e925f

924f336b33c35e26a2cbfa7915d65a6c2b5d58a1f77adb81dadd4035f101276a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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