Which versions of slnproxy461998 are malicious?

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

How do I remediate slnproxy461998 if I installed it?

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

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

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

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

Malicious package

slnproxy461998RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8726

Immediate action

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

gem uninstall slnproxy461998

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6b0457f3f1bc2dd32126126f899f64f52826c64caeb494a23008eea5e6ac5770

f9b69a82c1e81b9da57969128b7559edccd173c55b6a4ba52d7ee0f52c611cd6

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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