Which versions of vfsrce18 are malicious?

The following PyPI versions of vfsrce18 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate vfsrce18 if I installed it?

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

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

Yes — vfsrce18 is associated with the RLMA-2025-02614, GENERIC-standard-pypi-install-pentest, RLUA-2026-00891 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 vfsrce18 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 vfsrce18 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vfsrce18 across your stack and pipelines.

Malicious package

vfsrce18PyPI

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

MAL-2025-4256

Immediate action

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

pip uninstall vfsrce18

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.0.0

Indicators of compromise (SHA-256)

3188bad020ceddacc75cd95bfad72021d76e3da5d0d77aee0f801b139f2a8e92

836b7cf6d793987cbcfa49089d1555f5331db1ee5debe2b92593be37032922f2

e469759fd14d2b1207e5da1f724c19e6dc6b2896feaf658ad78c4ad33e3748de

21cc578b4b539539f080731ad95f6c53689884e7725f675e020cc5419b7d3c60

5efe1768ebc6bb8f04405262a670dc71ed34715e4f17126848153ed66593cf6f

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 vfsrce18 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vfsrce18 across your stack and pipelines.
If you installed it — respond
vfsrce18 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 vfsrce18 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 vfsrce18 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. vfsrce18 on PyPI has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-02614GENERIC-standard-pypi-install-pentestRLUA-2026-00891

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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