Which versions of slnfive8130 are malicious?

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

How do I remediate slnfive8130 if I installed it?

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

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

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

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

Malicious package

slnfive8130RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8677

Immediate action

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

gem uninstall slnfive8130

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

1652441a887821dd736484abd6e7012927039fd338ab902a03f560a32d66cd09

f6cf28d5306ec7b592bc011f8e9921c7dc5d9235f79a7ac42c08aec2a0d4d8ff

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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