Which versions of vcsbzrx1 are malicious?

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

How do I remediate vcsbzrx1 if I installed it?

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

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

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

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

Malicious package

vcsbzrx1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9111

Immediate action

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

gem uninstall vcsbzrx1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

56c1ef21315cc2afd229f2604d4bf18fb9abe2fefc939b1f52642a4379178c7e

8c6650287a2f2bb4030268a619e668803cafe0e263c94dfc6b877a3f6716148f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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