DeltaPrime, a decentralized borrowing protocol and crypto broker, has been hit by a significant security breach resulting in over $6 million in losses. The exploit, identified by blockchain security firm Cyvers, affected the Arbitrum version of the platform and is attributed to a private key leak.
Incident Description
Several blockchain security experts noted that the hacker had gained control of the DeltaPrime admin proxy. This access enabled the attacker to upgrade the proxy and direct it toward a malicious contract, draining multiple liquidity pools including DPUSDC, DPARB, and DPBTCb. Cyvers confirmed the exploit and shared on X that they detected 'multiple suspicious transactions' related to DeltaPrime. According to the firm, the incident occurred because the admin lost control of a private key, allowing unauthorized access to platform funds. As a result, users were temporarily unable to withdraw their assets from the Arbitrum version of DeltaPrime.
Platform Response
The DeltaPrime team responded promptly by informing users via Discord and X about the issue and assuring the community that they were working on a resolution. 'The risk is contained, we’re working on asset retrieval and the insurance pool will cover any potential losses where possible,' said the team in the X post, adding, 'Additionally, we’re looking into other ways to reduce user losses to a minimum.'
Previous Incidents
This incident marks the second significant breach for DeltaPrime in recent months. In July 2024, the protocol suffered a $1 million hack due to a misconfiguration, which allowed an attacker to take over accounts, repay loans, and withdraw collateral. Following the previous exploit in July, the DeltaPrime team re-audited its codebase and assured users that vulnerabilities had been patched. However, the recurrence of another major breach raises concerns about the platform’s security measures.
The second major breach raises questions about the effectiveness of DeltaPrime’s security measures. The team continues to work on asset retrieval and minimizing user losses.
Comments