Which versions of slncvfyewd are malicious?

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

How do I remediate slncvfyewd if I installed it?

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

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

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

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

Malicious package

slncvfyewdRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8667

Immediate action

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

gem uninstall slncvfyewd

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

2de6ca1524926ca2c45348a75f5a211036ce953d530787a7eba1fdc0fbdadd58

1464c4411cf6f1e63f020656671dda9fb4fdd2391a25ce7e3280da5c99cd3dd0

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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