Which versions of handyfiles are malicious?

The following PyPI versions of handyfiles are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate handyfiles if I installed it?

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

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

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

Malicious package

handyfilesPyPI

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

MAL-2024-12282

Immediate action

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

pip uninstall handyfiles

What this malware does

During the installation, the package iterates its files and attempts to import a hidden module - which is embedded as ZIP archive in the image file

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

Campaign: 2024-12-handyfiles

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.
obfuscation

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ff07706cf12a9e367be39e539835ae8ee32652676ab1837588447db7871e60bb

381cd796d4e5fce8fb62c337374b5303e0b2466d67467efc95cbc4d7d8248dd4

7efccb64b4cdd8fb7874c44d3a4fc5d80cfcb38076c5bf26250310dddef5d4ee

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

Campaign

2024-12-handyfiles

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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