Which versions of mvv12 are malicious?

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

How do I remediate mvv12 if I installed it?

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

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

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

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

Malicious package

mvv12RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8105

Immediate action

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

gem uninstall mvv12

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

055f5de40f6612d2820da28754960f725beb2a510229568f5d18ad822e2e0848

065ca1f22a034b83b73fd52bd7a7dfff264378f5895718855ea6c70b3c34b7c2

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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