Which versions of slnccbvjvj are malicious?

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

How do I remediate slnccbvjvj if I installed it?

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

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

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

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

Malicious package

slnccbvjvjRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8655

Immediate action

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

gem uninstall slnccbvjvj

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f54174e5d6fcfa431222e461b9edfe9c7a790e084286b9fad22d2b2c1f6e63d0

2f7600279a7d77fece57f8eb648c7c8798ff14406b182789a1ab5bce1dfd9669

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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