Which versions of filespath are malicious?

The following PyPI versions of filespath are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate filespath if I installed it?

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

If filespath was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is filespath part of a known attack campaign?

Yes — filespath 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 filespath across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for filespath (version 1.0.0).

Malicious package

filespathPyPI

Advisory published Feb 3, 2026Updated Feb 3, 2026

filespath is a confirmed malicious PyPI package (MAL-2026-701) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in filespath (PyPI)

MAL-2026-701

Immediate action

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

pip uninstall filespath

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

1 flagged

1.0.0

Indicators of compromise (SHA-256)

556cf54f0093609b5c80263f0ba00056293592e66eb2a212454692e9cca38a35

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for filespath (version 1.0.0).
If you installed it — respond
filespath 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 filespath was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. filespath on PyPI has been identified as a malicious package (version 1.0.0 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 filespath-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

Explore

All malware advisories How O3 detects malware Vulnerability database