Which versions of vfsrcetest are malicious?

The following PyPI versions of vfsrcetest are flagged malicious: 1.1. Treat any of these as compromised.

How do I remediate vfsrcetest if I installed it?

vfsrcetest is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed vfsrcetest — how do I know if it already compromised me?

If vfsrcetest was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is vfsrcetest part of a known attack campaign?

Yes — vfsrcetest is associated with the RLMA-2025-02615, GENERIC-standard-pypi-install-pentest, RLUA-2026-00892 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 vfsrcetest across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for vfsrcetest (version 1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vfsrcetest across your stack and pipelines.

Malicious package

vfsrcetestPyPI

Malicious code in vfsrcetest (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-4257

Immediate action

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

pip uninstall vfsrcetest

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

1.1

Indicators of compromise (SHA-256)

cf6dde6193ab9d2066190523347c2f9cd6d6c7e8f5c702922bcebf3ae1426f99

866e6ebf7fed17a0509cca94af21d8d507c0da055978dcf42f14ea15786ff87b

7df901b4edfbd807ba2046d52cb63fb5c952df8c0bb464d1faff3f3732680ffc

07b33af987a8bbb9a871da151ff6e4b92990263bfc2ce72837d7cc8773206fea

1da41ddf90f0e97842b8dbff15c37b912fbd251e3ecf32f4f08415d68dad2e99

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for vfsrcetest (version 1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vfsrcetest across your stack and pipelines.
If you installed it — respond
vfsrcetest is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If vfsrcetest was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks vfsrcetest before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. vfsrcetest on PyPI has been identified as a malicious package (version 1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-02615GENERIC-standard-pypi-install-pentestRLUA-2026-00892

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks vfsrcetest-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring