Which versions of mvv7 are malicious?

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

How do I remediate mvv7 if I installed it?

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

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

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

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

Malicious package

mvv7RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8111

Immediate action

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

gem uninstall mvv7

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8d6d5552d388fb49b66d234645eb15495dbbeb72d674a9b77918ebfaa1bcb7d2

414d10c3751c78ae7ca2c7875a1ae1a25f0d9b78a9d1860a6a146da7ceb76392

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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