Which versions of oaitsvnxpamle are malicious?

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

How do I remediate oaitsvnxpamle if I installed it?

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

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

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

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

Malicious package

oaitsvnxpamleRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8351

Immediate action

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

gem uninstall oaitsvnxpamle

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

382d1d56206f41abee9237961621ffaaebd85e9ef05103b9708a8ffb4db612c0

d166161ef1ddc52cde459d8cb1e91b2c5cd8704d917b29e855d446d50ca617bb

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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