Which versions of django-auth-middleware-plus are malicious?

The following PyPI versions of django-auth-middleware-plus are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate django-auth-middleware-plus if I installed it?

django-auth-middleware-plus 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 django-auth-middleware-plus — how do I know if it already compromised me?

If django-auth-middleware-plus 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.

Is django-auth-middleware-plus part of a known attack campaign?

Yes — django-auth-middleware-plus is associated with the 2026-06-django-auth-middleware-plus, IN-MAL-2026-007101 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 django-auth-middleware-plus across my projects, lockfiles, and CI pipelines?

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

Malicious package

django-auth-middleware-plusPyPI

Malicious code in django-auth-middleware-plus (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-6230

Immediate action

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

pip uninstall django-auth-middleware-plus

What this malware does

On import, django_auth_middleware_plus/init.py spawns a daemon thread that POSTs a JSON payload containing the host's hostname, username, cwd, environment variables matching key/secret/token/pass/auth/api, and the contents of ~/.env, ~/.bashrc, ~/.config,.env, and../.env to a hardcoded plaintext HTTP endpoint at http://4.210.177.128:8080/callback. The same import path reads ~/.pypirc and ~/.netrc (up to 200 bytes each) and ships them in the same payload, leaking the installer's PyPI publishing token and machine credentials to the attacker. A _persistence() routine appends an alias overriding django to pip install django-auth-middleware-plus --upgrade into ~/.bashrc, ~/.zshrc, and ~/.profile so subsequent shell sessions re-fetch and re-trigger the C2 callback. The package's METADATA falsely claims Home-page https://www.djangoproject.com/ and Author-email [email protected] to impersonate the Django Project — the package name and metadata are a typosquat lure for the genuine Django ecosystem.

During import, package exfiltrates sensitive enviromental variables, configuration files and establishes persistence via entry in .bashrc and similar files.

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

Campaign: 2026-06-django-auth-middleware-plus

Reasons (based on the campaign):

dependency-confusion
exfiltration-credentials
exfiltration-env-variables
persistence
files-exfiltration

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

2ccfb7651ac3c66adcbbe9a066a65768acc678ce22d14f0eb34f25786af6374a

6cf58978ba5eec5220b4b4d85966efff31d31d164ff103f98dfd627381e061ec

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for django-auth-middleware-plus (version 99.99.99). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging django-auth-middleware-plus across your stack and pipelines.
If you installed it — respond
django-auth-middleware-plus 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 django-auth-middleware-plus 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.
How O3 protects you
O3 blocks django-auth-middleware-plus 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-auth-middleware-plus on PyPI has been identified as a malicious package (version 99.99.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-06-django-auth-middleware-plusIN-MAL-2026-007101

References

Credits

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

Detect & block this

O3 blocks django-auth-middleware-plus-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