Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

django-b64-imgPyPI

Malicious code in django-b64-img (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-3413
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall django-b64-img

What this malware does

The package provides a special image-storing field for Django REST Framework based on a legitimate implementation from the Hipo/drf-extra-fields repository. The malicious modification appends the cloud credentials and full settings values to the serialized form of specific image types. This way, an attacker can retrieve sensitive values by downloading back once uploaded image.

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

Campaign: 2026-05-old-django-b64-img

Reasons (based on the campaign):

  • exfiltration-credentials

  • obfuscation

  • backdoor

Malicious versions

1 flagged
1.1

Indicators of compromise (SHA-256)

f5ebdaebc61cf7a888322348e074f219519b7d09a24ab91732d8bc5061d86b2e

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for django-b64-img (version 1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging django-b64-img across your stack and pipelines.

  2. If you installed it — respond

    django-b64-img 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.

  3. Did it already run?

    If django-b64-img was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks django-b64-img before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. django-b64-img on PyPI has been identified as a malicious package (version 1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-05-old-django-b64-img

References

Credits

  • Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks django-b64-img-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

django-b64-img (PyPI) malicious package — MAL-2026-3413 | O3 Security