Which versions of vcsfossilx1 are malicious?

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

How do I remediate vcsfossilx1 if I installed it?

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

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

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

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

Malicious package

vcsfossilx1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9114

Immediate action

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

gem uninstall vcsfossilx1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a486c08079a77de163b7e769158371badfa76c831d423dcb932fac569f8ca840

69ab330618a3007773dfb461e4f5af368cabe1c9acd741451853d37ee0bf9e13

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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