Which versions of pydanticc are malicious?

The following PyPI versions of pydanticc are flagged malicious: 0.1.1, 0.1.2, 0.2.0, 0.3.0. Treat any of these as compromised.

How do I remediate pydanticc if I installed it?

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

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

Yes — pydanticc is associated with the 2026-08-flasq, IN-MAL-2026-016901, IN-MAL-2026-016905, IN-MAL-2026-016900, IN-MAL-2026-016904 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 pydanticc across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for pydanticc (4 malicious versions).

Malicious package

pydanticcPyPI

Advisory published Aug 7, 2026Updated Aug 7, 2026

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

Malicious code in pydanticc (PyPI)

MAL-2026-13489

Immediate action

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

pip uninstall pydanticc

What this malware does

pydanticc is a typosquat of the popular 'pydantic' package. Its setup.py defines a custom setuptools install command whose body is stored as a base64 string literal and reconstituted at install time via base64.b64decode + compile + exec, concealing the payload from plain reading of setup.py. On Linux, the decoded hook downloads an opaque executable from https://github.com/totti2188/8gp1Q7iZD3h4VW/releases/download/v1.3A/something (a personal GitHub account unrelated to the package's stated purpose), writes it to /tmp/something, marks it executable, and launches it detached via subprocess.Popen with start_new_session=True. The shipped Python module (djangoo/main.py) contains only a trivial hello() print with no pydantic-related functionality, so the package's real effect on installation is arbitrary remote code execution on the installer's host. The unpinned personal-account release URL, base64/exec obfuscation of the URL and Popen call, detached background execution, name-squat of a top-100 package, and stub content together constitute a classic install-time dropper.

Package imitates name of a popula library. During installation, obfuscated code downloads a malicious executable and starts it. It then exfiltrates at least cryptocurrency wallet data, probably more.

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

Campaign: 2026-08-flasq

Reasons (based on the campaign):

typosquatting
The package overrides the install command in setup.py to execute malicious code during installation.
exfiltration-generic
Downloads and executes a remote executable.
obfuscation
exfiltration-crypto

Malicious versions

4 flagged

0.1.10.1.20.2.00.3.0

Indicators of compromise (SHA-256)

c16b176d1ba6ee3f4f1680d0678c9933e620f4de18bec7bc9af67978ed737527

faf0b5d83a6387044068dd0d4eb61cef977123164e4be406b16bf2c38ac4f9ed

0b849ee630b66e8839acdf0c7830372ba690b80f182434aea2816513ee2b35ad

0bc3a091548db52bab3bf8556e95780b3041aa971b6353d7f31bdb71128915a1

341e293bf68c074727878e98df5cad5aad9f711aca022d4e95b5e7723adf4a88

924a5e8609b73977255f604d1e6f55179d72569ffb2698c8c54af1b258b36a90

Detection & response playbook

Credential / info stealer

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

Campaign

2026-08-flasqIN-MAL-2026-016901IN-MAL-2026-016905IN-MAL-2026-016900IN-MAL-2026-016904

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

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