Hinkal Reported Exploited For $820K As Funds Move To Tornado Cash And Bitcoin

Specter flagged an alleged Hinkal Protocol exploit of about $820,000, with attacker-linked funds moving through Tornado Cash and THORChain shortly after the incident.

The onchain trail listed 410 ETH, worth about $700,000, deposited into Tornado Cash. Another 44.7 ETH moved from Ethereum to a Bitcoin address beginning with bc1qr2sf and ending in zn3w through THORChain.

The alert did not include a confirmed postmortem from Hinkal, an exploit transaction breakdown, or a root-cause explanation. The incident is therefore best framed as an onchain-investigator alert until Hinkal or an independent security firm publishes a fuller technical report.

Hinkal is a privacy-focused protocol for private transfers and shielded onchain activity. Its whitepaper describes an Ethereum zero-knowledge privacy system that accepts ETH and ERC-20 deposits so users can later withdraw, transfer, swap or stake without directly linking the later action to the original deposit.

Funds Split Between Mixer And Cross-Chain Route

The attacker-linked movement followed two separate paths. The larger portion went into Tornado Cash, a mixer that breaks the visible link between deposit and withdrawal addresses. The smaller portion used THORChain to move ETH value into Bitcoin.

That split leaves investigators tracking both mixer deposits and cross-chain settlement. Tornado Cash deposits keep the value on Ethereum while weakening direct address attribution. THORChain moves the value into native Bitcoin, where the receiving address and later UTXO movement become the next visible trail.

The pattern is similar to other recent laundering phases after DeFi incidents. Wallets tied to the UXLINK exploit sent 3,700 ETH into Tornado Cash after earlier conversions into liquid assets. KelpDAO’s attacker also routed funds through Tornado Cash and THORChain as the recovery window narrowed.

These examples do not establish attribution for the Hinkal incident. They illustrate a recurring investigative constraint: once funds move into privacy tools or across chains, attribution becomes significantly harder, and recovery typically depends on subsequent errors, identifiable exchange interactions, frozen chokepoints, or direct intervention by affected projects.

Root Cause Still Unconfirmed

The reported loss stands near $820,000, with about 410 ETH deposited into Tornado Cash and 44.7 ETH bridged from Ethereum to Bitcoin through THORChain. No official exploit cause has been confirmed in the public alert.

The incident could involve a protocol-level issue, compromised keys, user-facing infrastructure, malicious approvals, or another access path. Without a technical postmortem, the available facts are limited to the reported loss estimate, the attacker-linked fund movements and the laundering routes.

Hinkal users and integrators will need the project’s confirmation before the affected contracts, wallets, chains, user groups or recovery steps can be stated with certainty. As of the Specter alert, the visible movement included 410 ETH into Tornado Cash and 44.7 ETH routed through THORChain to a Bitcoin address.

The post Hinkal Reported Exploited For $820K As Funds Move To Tornado Cash And Bitcoin appeared first on Crypto Adventure.