Which versions of slnproxyxyzabc are malicious?

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

How do I remediate slnproxyxyzabc if I installed it?

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

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

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

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

Malicious package

slnproxyxyzabcRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8729

Immediate action

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

gem uninstall slnproxyxyzabc

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b73e28b3175e04396b5630af00707150f076e703b895fd4233cb148333d0dacb

65db13774ff0adfe03192b722756fcf499b514ecfdebb57931847a32ecda2c58

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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