Which versions of slproxy1778551587 are malicious?

The following RubyGems versions of slproxy1778551587 are flagged malicious: 0.0.1, 0.0.2, 0.0.3. Treat any of these as compromised.

How do I remediate slproxy1778551587 if I installed it?

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

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

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

Search your lockfiles and build artifacts for slproxy1778551587 (3 malicious versions).

Malicious package

slproxy1778551587RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

slproxy1778551587 is a confirmed malicious RubyGems package (MAL-2026-8768) that executes malicious code on install (malicious versions 0.0.1, 0.0.2, 0.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in slproxy1778551587 (RubyGems)

MAL-2026-8768

Immediate action

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

gem uninstall slproxy1778551587

Malicious versions

3 flagged

0.0.10.0.20.0.3

Indicators of compromise (SHA-256)

fc71ec34129cadf47c283056e1897b1bd7533e1d0319e6c3fa6356a9ef62756a

aff4b0be3fca68ebd42a2e54f33fcd17ac74742e58abced77e8b8bd6cc4642cb

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for slproxy1778551587 (3 malicious versions).
If you installed it — respond
Remove slproxy1778551587 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 slproxy1778551587 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. slproxy1778551587 on RubyGems has been identified as a malicious package (versions 0.0.1, 0.0.2, 0.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-03419RLUA-2026-09317

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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