Which versions of oaifx1955773 are malicious?

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

How do I remediate oaifx1955773 if I installed it?

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

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

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

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

Malicious package

oaifx1955773RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8192

Immediate action

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

gem uninstall oaifx1955773

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

fc5e12bb20836dc38a9d322e857889d87226dfcfa1d6d0f9deef38cd80a3b49d

5ba9ed311896f5a7b2d49997d302c242c5813ab93fb018754250336649c78bc0

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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