Which versions of vsc-config are malicious?

The following PyPI versions of vsc-config are flagged malicious: 4.0.0. Treat any of these as compromised.

How do I remediate vsc-config if I installed it?

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

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

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

Malicious package

vsc-configPyPI

Malicious code in vsc-config (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-11748

Immediate action

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

pip uninstall vsc-config

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

4.0.0

Indicators of compromise (SHA-256)

0d2a2aad15094a4c9500633cce8162c21706d47537e3626f883ad780ffc6ebf6

0dae2b42fd0a9c5024b8546985b5717e8d8b96bbea8995c3395828431cd0c58e

c2ec1c70e372eda0ea5a9836df505e286be87f7259eb91e6b3d2fb81928dbcba

e14383d7af409f89c91fa528da75814caa5a523eef7d6b05fdda4f3bd29faf93

a84b6575f32d842152de89b2c08ed9e4fe55a461b0145a9fc814c2d17879a073

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

Campaign

RLMA-2024-11209GENERIC-standard-pypi-install-pentestRLUA-2026-00898

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks vsc-config-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