Which versions of rootmv26543 are malicious?

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

How do I remediate rootmv26543 if I installed it?

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

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

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

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

Malicious package

rootmv26543RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8539

Immediate action

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

gem uninstall rootmv26543

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

07fe15f6a2db5cd92e3934782b1acf7ce3b630533c3f82f1ef68fbc6d0f895e0

ba271c0a72040dea500ac514ad59cca01ae5faeac4d45b841d38e8b296d4720f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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