Which versions of roottestkey10726 are malicious?

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

How do I remediate roottestkey10726 if I installed it?

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

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

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

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

Malicious package

roottestkey10726RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8541

Immediate action

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

gem uninstall roottestkey10726

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8ac54b91f981d812b5f4b308bcbe188a4c73815b6fbd9760a8fd093c677b4357

edf648d9b11868ca9da1e54c7f41fc25574e7fc662fa7862fd3a0cbab2b33b0d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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