Which versions of mvv6 are malicious?

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

How do I remediate mvv6 if I installed it?

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

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

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

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

Malicious package

mvv6RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8110

Immediate action

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

gem uninstall mvv6

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b5551322ba795053466e1f1d788939e918ba7a026f1b5be2579ecd71c743369e

9ac7a3d81fa5ab723bbbfc83f3ceb3ef3d6da25802b97abf963a821f5f5ca2c1

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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