Which versions of mvv4 are malicious?

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

How do I remediate mvv4 if I installed it?

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

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

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

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

Malicious package

mvv4RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8108

Immediate action

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

gem uninstall mvv4

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e44d811acff58622a7ecd07c3c034a703b82df8e3e75eaca650d6832113f8b9e

b96b4a8159cb7fdaa800e922411074811cc761ed3c3874ab921aea7c76b2dc02

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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