Which versions of hancsv are malicious?

The following PyPI versions of hancsv are flagged malicious: 1.2. Treat any of these as compromised.

How do I remediate hancsv if I installed it?

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

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

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

Malicious package

hancsvPyPI

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

MAL-2025-191748

Immediate action

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

pip uninstall hancsv

What this malware does

Importing the module triggers downloading and executing Powershell script. The script collects information about the host (including e.g. startup applications) and also downloads the next stage executable.

While the package contains a security disclaimer, the behaviour is still malicious and crosses the researching line.

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

Campaign: 2025-06-hancsv

Reasons (based on the campaign):

Downloads and executes a remote malicious script.
Downloads and executes a remote executable.
The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.

Malicious versions

1 flagged

1.2

Indicators of compromise (SHA-256)

ab165fde7f7a8a49c8b7f1e0d96e13a69f04af0e499373cc0925c5fc23c5be96

bb3fdca931bea8323cd7a8c2578f6d0c0594b3ea1b30df1819830168fe90983b

119b3a03641ebbc3e89a0bc40e45b5146b6f61b9523cbcc18216015259f74fa7

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

Campaign

2025-06-hancsv

References

Credits

Kamil Mańkowski (kam193)

Detect & block this

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