Which versions of mvv11 are malicious?

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

How do I remediate mvv11 if I installed it?

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

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

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

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

Malicious package

mvv11RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8104

Immediate action

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

gem uninstall mvv11

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b474393eaa227bba33e5132f3cc23befdff83b3a41a647d1dc85ce9987684070

80d8449610219b290722e082ba663474f7d5bd51e393bda2ed129ca0c9e16274

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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