Which versions of oaiztestxyz123 are malicious?

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

How do I remediate oaiztestxyz123 if I installed it?

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

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

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

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

Malicious package

oaiztestxyz123RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8354

Immediate action

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

gem uninstall oaiztestxyz123

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

fd31670b5731c79acb0dd9241c8496844f4420070892a962d9afebd46a42f3d4

9853be453914b5808e98801fff286ffe3dbd30a7ca1eacdf7ec750b49760c36a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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