Which versions of slvan668 are malicious?

The following RubyGems versions of slvan668 are flagged malicious: 0.0.2. Treat any of these as compromised.

How do I remediate slvan668 if I installed it?

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

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

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

Search your lockfiles and build artifacts for slvan668 (version 0.0.2).

Malicious package

slvan668RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

slvan668 is a confirmed malicious RubyGems package (MAL-2026-8788) that executes malicious code on install (malicious version 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in slvan668 (RubyGems)

MAL-2026-8788

Immediate action

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

gem uninstall slvan668

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

df24fa6a63d7684b5e985e7c6b9936cb31553a3a773ddadb3cf644ba828beb18

1cdcb959d87d2827b0d7636b6e81580c94df9bc4f2bb01281a6f5e1a3ef2a26e

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for slvan668 (version 0.0.2).
If you installed it — respond
Remove slvan668 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 slvan668 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. slvan668 on RubyGems has been identified as a malicious package (version 0.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-03439RLUA-2026-09337

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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