Which versions of oaihx0305933 are malicious?

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

How do I remediate oaihx0305933 if I installed it?

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

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

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

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

Malicious package

oaihx0305933RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8217

Immediate action

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

gem uninstall oaihx0305933

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

47b0edda22977db71a6454a45f10a848196064ae71cf236d7a66da363d32e2ea

7ef32375b11802294f9f44e789e9f247c0d5f6ea237515e9ce878a13496decb3

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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