Hinkal's privacy protocol has suspended affected smart contracts due to abnormal USDC transactions on the Ethereum blockchain.
Related
The decentralized privacy protocol Hinkal was found to have experienced suspicious transactions, resulting in the theft of 800,000 USDC.
PANews reported on July 3 that, according to CertiK Alert monitoring, suspicious transactions occurred in the decentralized privacy protocol Hinkal. The EOA address 0xbB3f01a1b1C68F3DEB36C55342b5F5706c32fc20 executed multiple "Transact" transactions after completing the "Proofless Deposit" operation, stealing approximately 800,000 USDC from the Hinkal contract.
hinkal will fully compensate users for their funds, confirming that approximately 797,000 USDC was withdrawn by attackers and exchanged for 454 ETH.
Mars Finance reports that the decentralized privacy protocol hinkal has released a security incident update, confirming that attackers withdrew approximately 797,000 USDC from its Ethereum contracts through a series of transactions and exchanged it for approximately 454 ETH. Of this, approximately 410 ETH was subsequently transferred to Tornado Cash, and the remaining approximately 44.67 ETH was transferred to the Bitcoin network via THORChain. The company is currently working with external security teams to track the flow of funds. hinkal stated that the impact of this security incident is limited to the relevant on-chain liquidity pools; other on-chain contracts were unaffected, but all contracts have been temporarily suspended for repairs and security verification. All affected users will receive full compensation on a 1:1 basis; the specific compensation process and timeline will be announced in a subsequent update.
Data: CertiK monitored an attack on Hinkal Protocol, resulting in the theft of approximately $800,000 in USDC.
According to Mars Finance, CertiK monitoring revealed suspicious transactions occurring on the decentralized privacy protocol Hinkal Protocol. Address (0xbB3...fc20) executed multiple "Transact" transactions after initiating a "Proofless Deposit," withdrawing approximately $800,000 USDC from the Hinkal contract.
Decentralized derivatives trading protocol Variational will launch swap contracts in the third quarter.
According to Foresight News , the decentralized derivatives trading protocol Variational will launch swaps in the third quarter to bring liquidity from traditional financial institutions to the on-chain market. The official team has already signed a cooperation agreement to provide over $1 billion in open interest (OI) capacity to the swap market and has begun connecting traditional financial liquidity to perpetual contracts for gold, silver, and WTI crude oil, narrowing related trading spreads by over 20%. According to a previous report by Foresight News , Fortune magazine reported that Variational completed a $50 million Series A funding round in May of this year, led by Dragonfly Capital.
Summer.fi An attack has been officially confirmed; all vaults in the Lazy Summer Protocol have been suspended.
According to Foresight News , Lazy Summer Protocol has officially confirmed an attack and has suspended all vaults under its umbrella. The cause is currently under investigation, and updates will be provided as they become available.
Echo Protocol has initiated a campaign to collect information on affected users of eBTC and is urging them to submit Discord support tickets.
According to Foresight News , the Bitcoin infrastructure protocol Echo Protocol tweeted that it has initiated information collection for affected users regarding the eBTC exploitation incident that occurred on Curvance. The team stated that it has conducted a preliminary investigation of affected addresses based on on-chain data and hopes to contact potentially affected users to verify information and negotiate solutions in order to advance subsequent processing. Affected users need to submit a support ticket on the official Discord platform, providing information such as the affected wallet address, assets, and amount. The registration period is two weeks after the announcement. Subsequent solutions will be determined after coordination with affected users, relevant platforms, and the protocol team, and will be implemented in a cautious and transparent manner.