Which versions of rootmtest14978 are malicious?

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

How do I remediate rootmtest14978 if I installed it?

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

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

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

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

Malicious package

rootmtest14978RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8537

Immediate action

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

gem uninstall rootmtest14978

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

566525c774cfd173bc978e66aaae43b5ec53b9f0feffeb305d77929d2fd61f1f

a8c8216da1c2136151fa63865003d32c35c386ee464ac82f38854deef3fbe3c2

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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