Which versions of vcsfossilpdfx1 are malicious?

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

How do I remediate vcsfossilpdfx1 if I installed it?

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

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

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

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

Malicious package

vcsfossilpdfx1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9113

Immediate action

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

gem uninstall vcsfossilpdfx1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

1b4f1a7efc9e7f7fde1a71751172887233a3510d49923c84fc733e70c4f3c691

5f0e5498f8755ee71caf3980b2be5bdda675ca550717240636870204fb6997af

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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