Which versions of metatestmyprfolx are malicious?

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

How do I remediate metatestmyprfolx if I installed it?

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

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

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

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

Malicious package

metatestmyprfolxRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8091

Immediate action

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

gem uninstall metatestmyprfolx

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

725421d6b5c33a674f22326b87de90d451c2f3aa9c010969317141d85a3e6120

60acab76f9a25d782fccb3765697b17cd92c9bfa7592c24be8223c3b544a1871

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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