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 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-healthchecks part of a known attack campaign?

Yes — starlette-healthchecks is associated with the 2026-09-starlette-healthcheck 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?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for starlette-healthchecks (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging starlette-healthchecks across your stack and pipelines.

Malicious package

starlette-healthchecksPyPI

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 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

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-healthchecks (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging starlette-healthchecks across your stack and pipelines.
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 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-healthchecks 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-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-healthcheck

References

bad-packages.kam193.eu

Credits

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