Which versions of slnfive8125 are malicious?

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

How do I remediate slnfive8125 if I installed it?

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

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

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

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

Malicious package

slnfive8125RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8676

Immediate action

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

gem uninstall slnfive8125

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d9299c0c31b46f31baef1e1c14bd2838f585893a248e54843531ce0d8deb9f2c

a6a93836ed8ab3bbde25f48ee3e5d685cd740743f793cdda49d78dee8a332d09

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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