Which versions of metatestfpepbeeo are malicious?

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

How do I remediate metatestfpepbeeo if I installed it?

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

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

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

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

Malicious package

metatestfpepbeeoRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8090

Immediate action

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

gem uninstall metatestfpepbeeo

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

4c4f26752346e2a0573708311002d518bb2afc92c5a938a4ab2558cb4ea183dd

cb8219e03a2d612b99ecc137747b914f94e76d07ac7e4e42d92b319405b001fd

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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