Which versions of oaithgxwnvon are malicious?

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

How do I remediate oaithgxwnvon if I installed it?

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

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

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

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

Malicious package

oaithgxwnvonRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8348

Immediate action

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

gem uninstall oaithgxwnvon

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d9dda8594657df636b1c6e8e13948198fdfce7c1081a5cd1ec51c9d75d2c7b07

adf647afba1264f0d16ccae7f19d2fe832e5de4c6710ac8222a8049b6e42bc3c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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