Which versions of hellospa are malicious?

The following PyPI versions of hellospa are flagged malicious: 90.0.0. Treat any of these as compromised.

How do I remediate hellospa if I installed it?

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

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

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

Malicious package

hellospaPyPI

Malicious code in hellospa (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191972

Immediate action

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

pip uninstall hellospa

What this malware does

Package exfiltrates credentials, env variables and other sensitive data on running. Notably, exfiltrated cloud credentials were immediately checked from a remote location.

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

Campaign: 2025-12-hellospa

Reasons (based on the campaign):

exfiltration-generic
exfiltration-env-variables
exfiltration-cloud-tokens
exfiltration-credentials

Malicious versions

1 flagged

90.0.0

Indicators of compromise (SHA-256)

276fd70d8b56465c07e6a06281b93ef014fcab93ce00be738e645501713dbdda

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

Campaign

2025-12-hellospa

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks hellospa-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