Which versions of sltestproxyabc are malicious?

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

How do I remediate sltestproxyabc if I installed it?

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

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

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

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

Malicious package

sltestproxyabcRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8786

Immediate action

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

gem uninstall sltestproxyabc

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d2062c4f068fb33abb5ecfa8a70bafed05d03b254620cab8f58b1f22e02c74d9

d65eafa17c2cec0d6cd4cc2839320266f116bcafdb8a2a73292fd21347b1348c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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