Which versions of djangoframework-test are malicious?

The following PyPI versions of djangoframework-test are flagged malicious: 3.3.3. Treat any of these as compromised.

How do I remediate djangoframework-test if I installed it?

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

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

Yes — djangoframework-test is associated with the 2025-01-just-framework 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 djangoframework-test 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 djangoframework-test (version 3.3.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging djangoframework-test across your stack and pipelines.

Malicious package

djangoframework-testPyPI

djangoframework-test is a confirmed malicious PyPI package (MAL-2025-191720) that steals credentials and exfiltrates sensitive data (malicious version 3.3.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in djangoframework-test (PyPI)

MAL-2025-191720

Immediate action

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

pip uninstall djangoframework-test

What this malware does

Importing the module exfiltrates basic information using DNS queries. There is no other purpose of the package.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2025-01-just-framework

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
dependency-confusion

Malicious versions

1 flagged

3.3.3

Indicators of compromise (SHA-256)

fca9db7649544820f5d4b1fc994fd9f6cf3391e3d34093457f685a159c64c88a

fe24a0d1142970bffbb9b8eba926e7153c78c87083aa7e374c146d9e1608aec4

00bd64503c29fcf25720ceaa3bc9ada93327afde72aee656545a31847ffabd76

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 djangoframework-test (version 3.3.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging djangoframework-test across your stack and pipelines.
If you installed it — respond
djangoframework-test 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 djangoframework-test 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 djangoframework-test 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. djangoframework-test on PyPI has been identified as a malicious package (version 3.3.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-01-just-framework

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks djangoframework-test-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