Which versions of slnproxy2774 are malicious?

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

How do I remediate slnproxy2774 if I installed it?

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

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

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

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

Malicious package

slnproxy2774RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8724

Immediate action

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

gem uninstall slnproxy2774

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

68172682f6762c28e69735ef235bc6e8fb3c91379d0c81efe7722c9e097658dc

38cc244a4e0a0ccfb5db92301e3a377d1c748cf55f06e1ed0bc7ff03dd8303aa

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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