Which versions of slnfive8140 are malicious?

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

How do I remediate slnfive8140 if I installed it?

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

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

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

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

Malicious package

slnfive8140RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8679

Immediate action

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

gem uninstall slnfive8140

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

52c61386e3315e2161aff2cfbcc92690b1e84d8921a484e275872eac4266e2f6

87d745dd3b914ab2525d8e221445a4db3d41207ce9a6e7c7c6330a953ca75f31

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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