Vultisig Fixes Critical ECDSA Signature Private Key Leak Vulnerability
Current overview (not historical)
Vultisig's ECDSA signature implementation contained a critical private key leak vulnerability. An attacker who had compromised one signer could leak reusable internal protocol seeds by sending multiple malicious signature messages and observing error responses from other signers, ultimately recovering other signers' shares and the full private key. Security firm ChainSecurity disclosed the issue on October 21, prompting Vultisig to release a fix. The update identifies malicious signer error codes 100-109 in the DKLS signature library on Android and iOS, maps marked participants to device IDs across session setup, message processing, and signature completion, blocks automatic retries, and displays warnings to users that they are no longer using the compromised device, thereby blocking the attack vector.
Written with AI from the reporting · updated 10/26/2026
Expand the detailed fact route and sources
Story route
A station-by-station route from the first public evidence onward; every station carries its own evidence and uncertainty.
- 1Unclassified fact stationAug 21, 00:00recorded Oct 27, 05:17single sourcerevised
Vultisig修复ECDSA签名私钥泄漏漏洞
Read original source ↗ CryptoSlateReplay this moment in the explorerEvidence & revisions · 1 source records
- Subject：
- vultisig
- Action：
- 发布安全更新修复私钥泄漏漏洞
- Object：
- ECDSA签名实现中的关键停止信号
- Occurred (fact side)：
- Aug 21, 00:00
- Published (valid side)：
- Oct 27, 05:10
- First seen (known side)：
- Oct 27, 05:17
Fact stationSingle source · one-sided claimRevisedCopy may have been revised later; time replay is bounded. Layer labels group reading only, not causation between layers.
Uncertainty marks flag where to check the sources; they are not proven causation.
Report timeline
Explore every side through dated source reports.
- CryptoSlateRelated fact: single sourceSource report revisedVultisig fixes critical private key leak in shared signing wallet after security researchers' disclosure
Report first recorded Oct 27, 05:17
Security researchers at ChainSecurity disclosed on Oct. 21 that Vultisig's ECDSA signing implementation mishandled a critical stop signal, allowing a compromised signer to recover the full private key through repeated error responses. The flaw involved an attacker sending many malicious signing messages and observing whether the other signer returned an error, which revealed bits of a reusable internal protocol seed. The August 21 updates to both Android and iOS versions now stop retries and identify the compromised device upon detecting the library's malicious-party error codes 100-109, rather than displaying a generic failure message and retrying up to three times.
Read original source ↗
Event activity trend
- Latest comparable
- 3
- Comparable peak
- 4Oct 28, 14:00
- 24h change
- –
The chart compares consistently observed participants only. Hover or tap to inspect each hour; use arrow keys to move between observations.
Event discussion
Reader opinions are hosted on GitHub Discussions; posting requires a GitHub account. Comments are not verified facts.