Which versions of filipt are malicious?

The following PyPI versions of filipt are flagged malicious: 0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.1.4, 0.1.5. Treat any of these as compromised.

How do I remediate filipt if I installed it?

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

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

Yes — filipt is associated with the 2026-11-filipt 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 filipt across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for filipt (6 malicious versions).

Malicious package

filiptPyPI

Advisory published Nov 3, 2026Updated Nov 3, 2026

filipt is a confirmed malicious PyPI package (MAL-2026-18580) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.1.1, 0.1.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in filipt (PyPI)

MAL-2026-18580

Immediate action

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

pip uninstall filipt

What this malware does

The package ships a malicious executable started during the building of a wheel/installation. It has been identified as malicious by multiple vendors.

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

Campaign: 2026-11-filipt

Reasons (based on the campaign):

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

Malicious versions

6 flagged

0.1.00.1.10.1.20.1.30.1.40.1.5

Indicators of compromise (SHA-256)

c7d24a42d93443e6dd0a5c3899e31e60624c1564a215ad84be99be1e811205ca

71274850343391005d2d9594031bd612ad45b58389feeb4e416481d3c8b5e3e2

ac208e914480dac86130a64e95150acb19051df83f5a716ed1f59f8c89d5b0bc

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for filipt (6 malicious versions).
If you installed it — respond
filipt 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 filipt 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. filipt on PyPI has been identified as a malicious package (versions 0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.1.4, 0.1.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-11-filipt

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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