Which versions of starlette-healthchecks are malicious?

The following PyPI versions of starlette-healthchecks are flagged malicious: 1.3.1, 1.3.2. Treat any of these as compromised.

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

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

If starlette-healthchecks was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is starlette-healthchecks part of a known attack campaign?

Yes — starlette-healthchecks is associated with the 2026-09-starlette-healthcheck, IN-MAL-2026-020331, IN-MAL-2026-020330 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-healthchecks across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for starlette-healthchecks (2 malicious versions).

Malicious package

starlette-healthchecksPyPI

Advisory published Sep 21, 2026Updated Sep 23, 2026

starlette-healthchecks is a confirmed malicious PyPI package (MAL-2026-16356) that steals credentials and exfiltrates sensitive data (malicious versions 1.3.1, 1.3.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in starlette-healthchecks (PyPI)

MAL-2026-16356

Immediate action

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

pip uninstall starlette-healthchecks

What this malware does

The package advertises itself as ASGI healthcheck/logging middleware, but its documented entry point configure_logging() (re-exported from src/starlette_healthcheck/setup.py via init.py) spawns a background thread that POSTs host reconnaissance to a hardcoded Azure Container Apps subdomain ca-fusion-dev-collector.victorioussmoke-2f009910.uksouth.azurecontainerapps.io, which the caller does not configure. The beacon iterates the entire os.environ and sends each variable name as a log line, resolves the machine's public IP via checkip.amazonaws.com, and sends the hostname. Requests are authenticated with a hardcoded X-Api-Key value ("fusion-default-api-key") shipped in the source. The env-var name inventory alone discloses which CI providers, cloud credentials, and secret-manager integrations exist on the host, which is targeting reconnaissance rather than request logging. Placing the exfiltration code in a module named setup.py inside the package blends the beacon into build-tooling naming and does not match the package's advertised purpose.

The package appears to be a typosquatting research attempt. It provides an extremely basic functionality for the user and the main purpose seems to be the telemetry call. Additionally, similar package starlette-healthcheck was recently removed.

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

Campaign: 2026-09-starlette-healthcheck

Reasons (based on the campaign):

action-hidden-in-lib-usage
typosquatting

Malicious versions

2 flagged

1.3.11.3.2

Indicators of compromise (SHA-256)

13c2438df5dfe3675f8861c03c803a273747135af8a70fc916235ad64d6cd22f

090da89e9cdd96102197fa3c5f16840adf89d67c49b6c22c8c8b0e8b6dd4296b

a188debacc12b8da66c5bee77726baaaa37477ae614186d5d73b05b667e7b92e

eebffb3f581b979c3e9a1dc0aef347111b50922326b2181cc9d2bc009c4e7021

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for starlette-healthchecks (2 malicious versions).
If you installed it — respond
starlette-healthchecks 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-healthchecks was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. starlette-healthchecks on PyPI has been identified as a malicious package (versions 1.3.1, 1.3.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-09-starlette-healthcheckIN-MAL-2026-020331IN-MAL-2026-020330

References

Credits

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

Detect & block this

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