Which versions of pyprig are malicious?

The following PyPI versions of pyprig are flagged malicious: 1.2.0, 1.2.1, 1.2.2. Treat any of these as compromised.

How do I remediate pyprig if I installed it?

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

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

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

Search your lockfiles and build artifacts for pyprig (3 malicious versions).

Malicious package

pyprigPyPI

Advisory published Nov 2, 2026Updated Nov 2, 2026

pyprig is a confirmed malicious PyPI package (MAL-2026-18490) that steals credentials and exfiltrates sensitive data (malicious versions 1.2.0, 1.2.1, 1.2.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pyprig (PyPI)

MAL-2026-18490

Immediate action

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

pip uninstall pyprig

What this malware does

Clone of a legitimate Pydantic package with the added downloading of a remote code. The remote code is delivered from the GitHub repository and unpacked as a new module and then called during initialization of any models (runner injected into cloned Pydantic code). During analysis, the remote code was just a placeholder.

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

Campaign: 2026-11-pyprig

Reasons (based on the campaign):

Downloads and executes a remote malicious script.
clones-real-package

Malicious versions

3 flagged

1.2.01.2.11.2.2

Indicators of compromise (SHA-256)

11f4beddcb42e2348d31d2ef0605d72198a28e796467c8afbac5c5c30d870315

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for pyprig (3 malicious versions).
If you installed it — respond
pyprig 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 pyprig 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. pyprig on PyPI has been identified as a malicious package (versions 1.2.0, 1.2.1, 1.2.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-11-pyprig

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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