Which versions of mvv3 are malicious?

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

How do I remediate mvv3 if I installed it?

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

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

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

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

Malicious package

mvv3RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8107

Immediate action

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

gem uninstall mvv3

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

bf428d2f7949ebe4c9150917d2d01d1246a6acad5d6aa10603967ad47d415b83

2203d9eee9db5f5e8bd363445a28e8147fff34a0296b35c6b2ebffbec750e499

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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