Which versions of oaifx7943598 are malicious?

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

How do I remediate oaifx7943598 if I installed it?

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

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

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

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

Malicious package

oaifx7943598RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8200

Immediate action

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

gem uninstall oaifx7943598

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

2d02b12cfe6734720665c8598f6e4b2582747f7b8842613c86f8058a94acfae1

355e99c64c735acecbec63c5ef6331893d2000c85bdeff16ccf1808cf49cf50e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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