Which versions of oaifx4260376 are malicious?

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

How do I remediate oaifx4260376 if I installed it?

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

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

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

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

Malicious package

oaifx4260376RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8196

Immediate action

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

gem uninstall oaifx4260376

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

db3f0a43165778e60f2bde89a7d1578a8560b5b144b10022d2a546f91bc1a14b

ef6f1eadc718d193c78030b3b69851bda90a330f4a83f1000830e843c75a1b0e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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