Which versions of mvv1 are malicious?

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

How do I remediate mvv1 if I installed it?

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

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

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

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

Malicious package

mvv1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8102

Immediate action

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

gem uninstall mvv1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c3248a7a99b9d199cdb78565040186526a34fffdf7667217c612ba09be060dc8

cb91dbf9670a1564ba668728658b315f2468d258c116fa1cf9a25a990d00d3f1

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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