Which versions of oaifx7303384 are malicious?

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

How do I remediate oaifx7303384 if I installed it?

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

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

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

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

Malicious package

oaifx7303384RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8199

Immediate action

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

gem uninstall oaifx7303384

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

850842f11a9ace6942e54817d7e011320425c1b4fb5caf186b5b5102561948fc

cd2ba84f4c6e93c1f4d33ee491638ba18b236c0a0d4f7f07a631b8c31c8f687a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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