Which versions of dev-server-python are malicious?

The following PyPI versions of dev-server-python are flagged malicious: 99.9.9. Treat any of these as compromised.

How do I remediate dev-server-python if I installed it?

dev-server-python 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 dev-server-python — how do I know if it already compromised me?

If dev-server-python 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 dev-server-python part of a known attack campaign?

Yes — dev-server-python is associated with the GENERIC-standard-pypi-install-pentest, RLMA-2025-06560, RLUA-2026-00262 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 dev-server-python 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 dev-server-python (version 99.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dev-server-python across your stack and pipelines.

Malicious package

dev-server-pythonPyPI

Malicious code in dev-server-python (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191717

Immediate action

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

pip uninstall dev-server-python

What this malware does

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

99.9.9

Indicators of compromise (SHA-256)

fbf14c237ce3bd2e89a35acd79942a0d2df56f2c6088ab680a22ab68e5ec186b

77df2294feff074b86c685e622e69901b80eb16fdbf60eb785a026318d84788e

512844bc74823a85f8230faf74178615c8ba17f12bb9d58877c94f9951388df7

da577671bebe9461db9ad7685c3063fb37bd535762c004f85f2c45cb553a61ae

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

Campaign

GENERIC-standard-pypi-install-pentestRLMA-2025-06560RLUA-2026-00262

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks dev-server-python-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