Which versions of django-pyyaml are malicious?

The following PyPI versions of django-pyyaml are flagged malicious: 20.17.15. Treat any of these as compromised.

How do I remediate django-pyyaml if I installed it?

Remove django-pyyaml from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed django-pyyaml — how do I know if it already compromised me?

If django-pyyaml 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.

How do I find django-pyyaml across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for django-pyyaml (version 20.17.15).

Malicious package

django-pyyamlPyPI

django-pyyaml is a confirmed malicious PyPI package (MAL-2023-1362) that executes malicious code on install (malicious version 20.17.15). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in django-pyyaml (PyPI)

MAL-2023-1362

Immediate action

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

pip uninstall django-pyyaml

What this malware does

The OpenSSF Package Analysis project identified 'django-pyyaml' @ 20.17.15 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

20.17.15

Indicators of compromise (SHA-256)

07b95436e2a145afcd7f459f6101c1d1b699d4d5842126d920fe77f700c8899b

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for django-pyyaml (version 20.17.15).
If you installed it — respond
Remove django-pyyaml from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If django-pyyaml 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. django-pyyaml on PyPI has been identified as a malicious package (version 20.17.15 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks django-pyyaml-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database