Which versions of slntestrootabc are malicious?

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

How do I remediate slntestrootabc if I installed it?

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

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

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

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

Malicious package

slntestrootabcRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8765

Immediate action

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

gem uninstall slntestrootabc

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c7770863bbdf9f396056442d9ab8e865dc870ed37bef6226d9a4633f96075f41

3156b77456078fc137271ded53856e2d341d507249fc31c553c047f1a92a369b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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