Unleash Protocol Hack Drains $3.9M After Multisig Exploit, PeckShield Reveals

The post Unleash Protocol Hack Drains $3.9M After Multisig Exploit, PeckShield Reveals appeared first on Coinpedia Fintech News

Blockchain security firm PeckShieldAlert reported a major hack involving Unleash Protocol, a decentralized platform built on Story Protocol, where an attacker drained around $3.9 million in user funds.

Here’s how the hack happened. PeckShieldAlert report revealed.

How the Unleash Protocol Hack Happened?

According to PeckShieldAlert, the attacker targeted Unleash Protocol’s multi-signature governance system. 

By doing so, the attacker gained unauthorized admin access and pushed through a contract upgrade that had not been approved by the core team. This change opened the door for funds to be withdrawn directly from the protocol.

After withdrawing the funds, the attacker bridged the assets to Ethereum and began breaking them into smaller chunks. 

On-chain data shows 1,337.1 ETH was deposited into Tornado Cash, a privacy tool often used to hide transaction trails. 

The repeated deposits, from small amounts to batches of 100 ETH, seem designed to hide the source of the stolen funds.

.article-inside-link {
margin-left: 0 !important;
border: 1px solid #0052CC4D;
border-left: 0;
border-right: 0;
padding: 10px 0;
text-align: left;
}

.entry ul.article-inside-link li {
font-size: 14px;
line-height: 21px;
font-weight: 600;
list-style-type: none;
margin-bottom: 0;
display: inline-block;
}

.entry ul.article-inside-link li:last-child {
display: none;
}

• Also Read :
•   2025 Becomes One of Crypto’s Worst Years After Massive Losses
•   ,

What Assets Were Affected in the Breach

In its official incident notice, Unleash Protocol confirmed that several assets were impacted during the exploit. These include WIP, USDC, WETH, stIP, and vIP. The team stressed that the withdrawals happened outside normal governance rules and were not approved internally.

Importantly, Unleash clarified that there is no evidence of any compromise to Story Protocol, its validators, or its core infrastructure. The issue appears limited strictly to Unleash-specific contracts and admin controls.

Unleash Protocol Immediate Response

Following the discovery, Unleash Protocol immediately paused all operations to prevent further damage. The team is now working with independent security experts and forensic investigators to identify the root cause.

Users have been advised to avoid interacting with Unleash Protocol contracts until further updates are shared through official channels. 

FAQs