Which versions of coldcard-helpers are malicious?

The following PyPI versions of coldcard-helpers are flagged malicious: 1.4.2. Treat any of these as compromised.

How do I remediate coldcard-helpers if I installed it?

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

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

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

Malicious package

coldcard-helpersPyPI

coldcard-helpers is a confirmed malicious PyPI package (MAL-2026-11516) that steals credentials and exfiltrates sensitive data (malicious version 1.4.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in coldcard-helpers (PyPI)

MAL-2026-11516

Immediate action

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

pip uninstall coldcard-helpers

What this malware does

When installing the package or importing the module, code starts a background task collecting sensitive data, like sensitive environment variables, private keys for cryptocurrency wallets, SSH keys, and so on to a Telegram channel.

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

Campaign: 2026-08-coldcard-helpers

Reasons (based on the campaign):

exfiltration-env-variables
exfiltration-ssh-keys
exfiltration-crypto
exfiltration-credentials
uses-telegram-bot
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

1.4.2

Indicators of compromise (SHA-256)

127a096109f7b5b2bbedf7f6a9fc2e7baa706e93704ebd52615e744a9838fbc3

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

Campaign

2026-08-coldcard-helpers

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks coldcard-helpers-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