Which versions of oaifx9741380 are malicious?

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

How do I remediate oaifx9741380 if I installed it?

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

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

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

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

Malicious package

oaifx9741380RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8207

Immediate action

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

gem uninstall oaifx9741380

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b7090834752b275fe644e11ef0d153d627e2576976294b74775232244f801086

6670024f405fa670be22cbe04d3c7cdd5a65b85529da9ecdd22298f5852372d4

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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