Which versions of svchost are malicious?

The following PyPI versions of svchost are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate svchost if I installed it?

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

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

Yes — svchost is associated with the 2026-04-pckg-sv 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 svchost 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 svchost (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging svchost across your stack and pipelines.

Malicious package

svchostPyPI

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

MAL-2026-2628

Immediate action

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

pip uninstall svchost

What this malware does

Code exfiltrates sensitive crypto wallet's files and sets up a keylogger trying to catch the password to the wallet

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-04-pckg-sv

Reasons (based on the campaign):

crypto-related
keylogger
exfiltration-crypto
persistence

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

a56926028e7e253a1ffb3ba27d6514a5cbc6b23964d7e1094846a895dd322656

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

Campaign

2026-04-pckg-sv

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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