Which versions of oaifx9269956 are malicious?

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

How do I remediate oaifx9269956 if I installed it?

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

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

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

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

Malicious package

oaifx9269956RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8204

Immediate action

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

gem uninstall oaifx9269956

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

489d5f4261219c047547b702907c43ab1a8d4bc2523ed9e898702ef167bdc89d

857388d74c66f1e207b8b5113e342ae212024f267db8031581b24ab6fcda5773

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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