Which versions of mvv0 are malicious?

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

How do I remediate mvv0 if I installed it?

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

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

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

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

Malicious package

mvv0RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8101

Immediate action

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

gem uninstall mvv0

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7e2efa562d9d7c13c3ebf5fc3642bfc3d401c51dd6831152467eddff93eeb940

b6c928647b9ad025112c7f079a0a052923fb24559e04e24492d259de1ed8ea1a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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