Which versions of psbt-helpers are malicious?

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

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

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

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

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

Malicious package

psbt-helpersPyPI

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

Malicious code in psbt-helpers (PyPI)

MAL-2026-11521

Immediate action

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

pip uninstall psbt-helpers

What this malware does

The code advertised as a firmware upgrader for hardware wallets in fact downloads an infostealer. The stealer searches the machine for cryptocurrency sensitive data (wallet files, seeds), browser data (passwords, cookies), all kinds of credentials (including tokens, passwords, SSH keys, TOTP seeds etc.), other sensitive files and current clipboard content. Data are exfiltrated, and the stealer configures persistence via scheduled tasks or LaunchAgent. The code deliberatly doesn't start in CI environments and checks if the system looks real.

Continuation of 2026-08-coldcard-helpers campaign. Related packages are used in malicious repository https://github.com/domaup/coldcard-poc

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

Campaign: 2026-08-psbt-utils

Reasons (based on the campaign):

infostealer
files-exfiltration
clipboard-stealing
exfiltration-ssh-keys
obfuscation
crypto-related
exfiltration-cloud-tokens
Downloads and executes a remote malicious script.
exfiltration-browser-data
exfiltration-crypto
exfiltration-credentials
persistence

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

394dea9d587ac1affba13c45ecfc28f5d005b2cb5f8b665dcf4591b60085a8ae

82a309d768af6a39f95bb4f7c9f5d8548a95f0074613985f49f0513420dae9fa

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

Campaign

2026-08-psbt-utils

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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