Which versions of pathfiles are malicious?

The following PyPI versions of pathfiles are flagged malicious: 1.0.1, 1.0.8, 1.0.9, 1.1.1. Treat any of these as compromised.

How do I remediate pathfiles if I installed it?

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

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

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

Malicious package

pathfilesPyPI

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

MAL-2026-696

Immediate action

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

pip uninstall pathfiles

What this malware does

Disguised as file system manipulation library, the package hides an obfuscated code to communicate with a Telegram channel. Though the usage is not known at the moment, the package is clearly created for data exfiltration

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

Campaign: 2026-02-pathfiles

Reasons (based on the campaign):

obfuscation
action-hidden-in-lib-usage

Malicious versions

4 flagged

1.0.11.0.81.0.91.1.1

Indicators of compromise (SHA-256)

a96d53709493a07432f8619b9ca322fef0fb4bf9080a02da7e8f6bc03353b3c0

2c8fab273f2136c763bb212071216bca9ac4ece66962e7afc14fa6d07cf67256

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

Campaign

2026-02-pathfiles

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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