Which versions of oaifx8889601 are malicious?

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

How do I remediate oaifx8889601 if I installed it?

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

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

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

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

Malicious package

oaifx8889601RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8203

Immediate action

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

gem uninstall oaifx8889601

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b349bef454d3f5c7cc1279b110b79cd0498a3c1c0946f19f65270b314fc1a5fa

f8e379ac970a077d6259302151060b3db98d4256e2945447e92bdd780970e9cf

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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