Which versions of oaifx1757803 are malicious?

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

How do I remediate oaifx1757803 if I installed it?

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

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

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

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

Malicious package

oaifx1757803RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8191

Immediate action

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

gem uninstall oaifx1757803

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

0a688d869f1ccde278dd84d7fa7fe886373504e3e918397338fe34e99e4ad61f

22a870047cbed61428f7caa788475d84c84ac06d8a24b34c0e75000f0e8cd799

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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