Which versions of oaifx2280367 are malicious?

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

How do I remediate oaifx2280367 if I installed it?

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

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

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

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

Malicious package

oaifx2280367RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8193

Immediate action

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

gem uninstall oaifx2280367

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

72c03c8d11dfde289af869c38286a2ac637661e4940e2dea6d9d31271b87ddde

0d9da2da5a4463703fdc0f34f5e88f0b1a04ba386ce3a319d2e39930d799f7ac

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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