Which versions of slncdmcgtq are malicious?

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

How do I remediate slncdmcgtq if I installed it?

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

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

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

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

Malicious package

slncdmcgtqRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8657

Immediate action

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

gem uninstall slncdmcgtq

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

88c1d148ac032b1f6a48208ceb0385332dd0ab563c0b2d3ed76772b5e96465ed

6199ac53eb9956b63fda8a1185f7386d616619071e241752ef840f7db0d4655f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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