Which versions of mvv5 are malicious?

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

How do I remediate mvv5 if I installed it?

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

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

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

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

Malicious package

mvv5RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8109

Immediate action

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

gem uninstall mvv5

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ff2d6aebe32d3a1f40ae95a9da608c4619593a132122851bcdebedd115e4f374

b879307a725c11e4b80013524ffcc1b1729c6305b430afa7205faee3a1381436

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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