Which versions of slnproxy478404 are malicious?

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

How do I remediate slnproxy478404 if I installed it?

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

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

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

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

Malicious package

slnproxy478404RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8727

Immediate action

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

gem uninstall slnproxy478404

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

abac4c4a6fbd194b9ef4fcf91fd1b87451c5e539dfe19bf25e79c82c4bd77fd0

ccd9c96f01695c7ba4c05757df8825d0e1aaa3eb8255485d74de952c74f43b43

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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