Which versions of metatestabcxyz are malicious?

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

How do I remediate metatestabcxyz if I installed it?

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

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

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

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

Malicious package

metatestabcxyzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8088

Immediate action

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

gem uninstall metatestabcxyz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

bbe4de73a302be50d32a8908f6a662a0857e7802015c88556751db46c38420fd

aaa9b1819fe837ea183f7d088f5f4a5d52bfbafaeb5e658b208207a840581d9e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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