Which versions of oaifx9677940 are malicious?

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

How do I remediate oaifx9677940 if I installed it?

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

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

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

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

Malicious package

oaifx9677940RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8206

Immediate action

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

gem uninstall oaifx9677940

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d2e729b9f12a5f817e1e70637eeead29b22f4e8bb2bdea79121bf8d7b81f6fa9

f6cc2c45e0083f579d2316477c4186bddcd52530b414fc50046c2aea359b0060

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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