Which versions of slnczcvlmn are malicious?

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

How do I remediate slnczcvlmn if I installed it?

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

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

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

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

Malicious package

slnczcvlmnRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8669

Immediate action

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

gem uninstall slnczcvlmn

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f4582e6e18bc9886642c0e2e7b1c76a016d87b2fd444508a134a6752cd3e7272

9d3694b11172901502a31bf760ff5051a8c33f45c29439f6a9f966f91330fd14

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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