Which versions of mvv2 are malicious?

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

How do I remediate mvv2 if I installed it?

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

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

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

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

Malicious package

mvv2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8106

Immediate action

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

gem uninstall mvv2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

2e11afbbd875594c0238b9cbd0f5638da67c834b910518d224e717315655aad9

c48e7b8dad92aa947801f298b0fd65fafa456ce3e3babab03682e41c6e831a5a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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