Which versions of helmet-fastapi are malicious?

The following PyPI versions of helmet-fastapi are flagged malicious: 1.2, 1.3, 1.3.1, 1.3.2, 1.3.3. Treat any of these as compromised.

How do I remediate helmet-fastapi if I installed it?

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

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

Yes — helmet-fastapi is associated with the 2025-04-helmet-fastapi 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 helmet-fastapi 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 helmet-fastapi (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging helmet-fastapi across your stack and pipelines.

Malicious package

helmet-fastapiPyPI

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

MAL-2025-191752

Immediate action

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

pip uninstall helmet-fastapi

What this malware does

Package contains hidden code adding a backdoor - a WebSocket path handler which will execute commands sent by an attacker knowing the path. In addition, it adds a log handler to remove related access logs.

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

Campaign: 2025-04-helmet-fastapi

Reasons (based on the campaign):

backdoor
obfuscation

Malicious versions

5 flagged

1.21.31.3.11.3.21.3.3

Indicators of compromise (SHA-256)

cde4ad41115adb4e499fc7867383ebf986e62fcfc2492dbf3ca4937e16178ed9

c1f805932ecbcd95197e98c6e2336eb773252abf5615fe135076d1848cb90395

4621e284dc1fd619aaafc15169540550f8e6e4405c01a66d44e1dec597cb4deb

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

Campaign

2025-04-helmet-fastapi

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks helmet-fastapi-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