Which versions of starlette-healthcheck are malicious?

The following PyPI versions of starlette-healthcheck are flagged malicious: 1.2.0, 1.3.0, 1.3.1. Treat any of these as compromised.

How do I remediate starlette-healthcheck if I installed it?

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

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

Yes — starlette-healthcheck is associated with the IN-MAL-2026-007906, IN-MAL-2026-007908, IN-MAL-2026-007907 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 starlette-healthcheck 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 starlette-healthcheck (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging starlette-healthcheck across your stack and pipelines.

Malicious package

starlette-healthcheckPyPI

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

MAL-2026-6724

Immediate action

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

pip uninstall starlette-healthcheck

What this malware does

The package presents itself as an ASGI healthcheck/request-logging utility, but its advertised configure_logging() helper (exposed from the top-level init.py) spawns a background thread that POSTs JSON to a hardcoded Azure Container Apps host at ca-fusion-dev-collector.victorioussmoke-2f009910.uksouth.azurecontainerapps.io. On invocation it (1) iterates os.environ and emits one record per environment variable name (values masked, but the key set discloses the deployment's secret/service layout — AWS_, DB_, vendor tokens, internal infra names), (2) resolves the host's public IP via checkip.amazonaws.com, and (3) sends the machine hostname. None of this is documented in the README or package metadata; the destination is author-controlled, with a default API key embedded in the client and an undocumented LOG_ENDPOINT override. The middleware code itself is a trivial local request-timing logger that does not require any of this telemetry. Author metadata is a generic alias ("ForbiddenFruit") with no homepage. The name is also a plausible-utility name in the ASGI healthcheck space, increasing the chance of incidental adoption.

Malicious versions

3 flagged

1.2.01.3.01.3.1

Indicators of compromise (SHA-256)

45d8da59826f5074d5b65d3b4733a4da6e7ce20167db9c14f7004e5fb7abe273

672111029a3528c1f0bdd93e7251f563e9994f9e725eacbe498d59e4d07e2314

9e534fd526f8d46ec03462e3dd7120bdf9871478650e3c4af7ab34d2234b23c6

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

Campaign

IN-MAL-2026-007906IN-MAL-2026-007908IN-MAL-2026-007907

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks starlette-healthcheck-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