Which versions of django-bkvision are malicious?

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

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

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

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

Yes — django-bkvision is associated with the GENERIC-standard-pypi-install-pentest, IN-MAL-2026-009366 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-bkvision 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-bkvision (version 1.2.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging django-bkvision across your stack and pipelines.

Malicious package

django-bkvisionPyPI

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

MAL-2026-6593

Immediate action

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

pip uninstall django-bkvision

What this malware does

setup.py executes a top-level function on pip install that collects host metadata (hostname, user, cwd, Python version, platform, pid, timestamp) and POSTs it as JSON to a hardcoded Lark bot webhook at open.larksuite.com. The same install-time code performs an HTTP GET to an internal-range IP (9.138.237.216/flag.html) and forwards the response status and up to 2KB of the response body to the same external webhook, turning every installer into an SSRF canary against the target's internal network. The package name is a dependency-confusion claim on an internal name referenced by TencentBlueKing/BKFlow's requirements.txt, so any environment that resolves django-bkvision==1.2.0 from public PyPI fetches this payload-bearing package instead of the intended internal one. README claims the behavior is gated by environment variables, but the install-time code path is unconditional.

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

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: GENERIC-standard-pypi-install-pentest

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.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

1.2.0

Indicators of compromise (SHA-256)

ced7d2a58351f0d92c7d11dbbf9de326ba96041f445cf607c0decba06297a5b5

60f6913309b46f7fc428e08267197a375885efc1b3c5660d7707ef70895f558c

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

Campaign

GENERIC-standard-pypi-install-pentestIN-MAL-2026-009366

References

Credits

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

Detect & block this

O3 blocks django-bkvision-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