Which versions of oaifx6387627 are malicious?

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

How do I remediate oaifx6387627 if I installed it?

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

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

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

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

Malicious package

oaifx6387627RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8197

Immediate action

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

gem uninstall oaifx6387627

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e25c0c999e4658e98497bc5fb65584d18209c606863348cd667b712c4e8fb289

eb08f42ac20258a5ed0d1b5d9b060957f308ebcf7a930e6babb18e63699688bf

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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