Which versions of slnproxy377155 are malicious?

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

How do I remediate slnproxy377155 if I installed it?

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

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

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

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

Malicious package

slnproxy377155RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8725

Immediate action

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

gem uninstall slnproxy377155

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ff0da0e1f44db32f2d936a6aa2c1d403c9fdd4565ac59107f0667c00a20bdd65

9a62041b33f585b21d0bb4def93039a989be8b7a04a06c2440c3a94d4a5ac6fd

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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