4000 L-BTC Created Without Collateral...3996 BTC Pegged Out

Approximately 4,000 L-BTC created without collateral on Liquid Network was pegged out to about 3,996 BTC. The incident was attributed to a software vulnerability and an automated approval structure for large withdrawals.
Blockstream announced on September 23 that the exploit occurred on September 6 at 10:53 PM KST (UTC+9), when a block in Liquid Network contained a transaction that exploited a range-proof verification cache error in Elements. The error allowed different verification inputs without length information to combine, creating identical cache keys and reusing previously verified results for other transactions.
This flaw enabled L-BTC with no actual collateral to be approved as legitimate assets on the network. Liquid Network issues 1:1 L-BTC when users deposit BTC, and burns L-BTC to redeem BTC from reserves. Attackers sent the exploited L-BTC through SideSwap's peg-out service, which processed it as a normal customer order and paid out 3,996.02 BTC.
SideSwap stated that at the time, there were no size limits, speed restrictions, issuance cap checks, deposit wallet history verification, or manual review procedures for the orders. Attackers first tested with small peg-outs of 2.5 L-BTC before submitting large orders. The online status of approval keys and automatic transfer of funds to customer addresses within the same block exacerbated the damage.
SideSwap explained that if keys had been kept offline, manual review processes implemented, and a delay procedure added, the funds might have remained under control for potential recovery. A payment limit or delayed approval system could have held large withdrawals, limiting the damage. However, it is unclear what specific limits would have stopped the attack.
Alpen revealed on September 22 that its AI security tool MASH traced the cause in Elements code within about an hour after the attack and replicated the attack path locally. However, this was a post-incident reconstruction; there's no proof it could have detected vulnerabilities before the attack. Alpen noted that neither the live binary nor the cache state at the time were confirmed.
Elements version 23.3.4 includes a fix adding length information to range-proof cache inputs and introduced a -norangeproofcache option to disable caching. While Liquid Network had previously deployed a patch for the range proof verification vulnerability, this analysis showed that code fixes alone don't address operational risks in withdrawal processes.
The incident highlighted that both code validation of consensus rules and operational controls for fund disbursement are necessary. Blockstream reported that approximately 3,400 BTC has been recovered since the attack, with about 602 BTC still under recovery efforts. Attackers claimed to be 'whitehats' via on-chain messages, but their identity and legal responsibility remain unverified.
As of September 24, it remains unclear whether remaining funds will be fully recovered or when Liquid Network's peg-out service will resume.
Korean Source
This article is an English localization of a Korean-language crypto news report. Original headline: 4000 L-BTC 무담보 생성…3996 BTC 페그아웃