Which versions of metatesttgukcriv are malicious?

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

How do I remediate metatesttgukcriv if I installed it?

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

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

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

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

Malicious package

metatesttgukcrivRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8092

Immediate action

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

gem uninstall metatesttgukcriv

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

87e64237588cdae9965787af45edf02260ae95c93d4f993a1687ff398a496c9d

a83429c69125069a6b72c4635f34b1a0bcf9a92262b61ed282cf6b54d86bcb03

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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