Which versions of rootmv25753 are malicious?

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

How do I remediate rootmv25753 if I installed it?

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

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

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

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

Malicious package

rootmv25753RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8538

Immediate action

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

gem uninstall rootmv25753

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3b52cdec64e2682817ad209230d34032d0a5d17c8397f23303f67d63072ad772

c5d176e9f9762f11e7607c5e30c694cf55932ba0d472d4b526b08a9cfdf0271e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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