Which versions of vcssvnx1 are malicious?

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

How do I remediate vcssvnx1 if I installed it?

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

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

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

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

Malicious package

vcssvnx1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9120

Immediate action

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

gem uninstall vcssvnx1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

51c032842a892c7d5c8cde9dd0f26c765e67b5ba96eb8ba3f74d9d22bed1c518

9364a3c452693932e3e90089fc7aa63c1f218708cc77b148937da467c097c63d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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