Which versions of filecraft are malicious?

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

How do I remediate filecraft if I installed it?

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

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

Yes — filecraft 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 filecraft 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 filecraft (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 filecraft across your stack and pipelines.

Malicious package

filecraftPyPI

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

MAL-2024-12272

Immediate action

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

pip uninstall filecraft

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)

e254f88b8d741f7a43a0e494dcfd08135f29b5634f3baa5d684b2bd6bc168bfc

3d0eec02526b659b5e856c211e05be1842dc283ed0b7d07dc90574ea5c7dc34a

3cc26897a4e79c8a9b10f1b628671a7e2af53733c3bc7ee8ca5eecdc6c97f450

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 filecraft (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 filecraft across your stack and pipelines.
If you installed it — respond
filecraft 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 filecraft 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 filecraft 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. filecraft 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 filecraft-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