HomeCII/OTLoss of $450K Caused by Withdrawal Flaw

Loss of $450K Caused by Withdrawal Flaw

Published on

spot_img

In the world of cryptocurrency, the recent cyberattack on Clipper, a decentralized exchange (DEX), has caused quite a stir within the community. The attack, which occurred on December 1, 2024, resulted in a loss of approximately $450,000 from the protocol. Initially, speculations arose that the breach was due to a private key leak, but Clipper has since clarified that the vulnerability was actually in its withdrawal functionality.

The exploit targeted Clipper’s withdrawal process on the Optimism and Base pools, impacting about 6% of the exchange’s total value locked (TVL). While the attacker attempted to target other chains, their efforts were unsuccessful. Fortunately, the exploit has now been contained, and an ongoing investigation is in place to track the stolen funds and potentially recover them.

Clipper wasted no time in responding to the breach, taking swift action to address the data breach by halting all swaps and deposits on its platform. Despite this, withdrawals were still operational with limitations in place. To mitigate further exploitation, Clipper disabled the ability to withdraw single assets, mandating users to withdraw a mix of all assets in the pool.

Furthermore, Clipper reassured its community that no other pools or chains were impacted by the attack. In an official statement, the exchange debunked claims of a private key leak, asserting that the breach was solely due to a vulnerability in the withdrawal feature. This vulnerability, specifically a bundled swap-and-withdraw function, allowed the attackers to withdraw more funds than they had deposited initially.

The cyberattack involved the unauthorized use of the API to sign transactions, enabling the attackers to manipulate the system and gain more tokens than they had originally put in. Suspicious transactions were detected, originating from a call on the Clipper Exchange’s pool deposit and withdrawal functions, facilitating the exploit.

In response to the incident, Clipper initiated a thorough investigation to fully comprehend the extent of the exploit and started efforts to trace and recover the stolen funds. The exchange has halted trading and deposits across all chains as a security measure to prevent further damage. However, Clipper assured its users that their funds were secure in the system and not at risk.

The exchange concluded its statement by reaching out to the exploiter, urging them to communicate directly for a potential resolution. As the investigation continues, Clipper remains committed to transparency, providing updates to the community as more information unfolds.

Overall, the Clipper cyberattack serves as a stark reminder of the vulnerabilities present in the cryptocurrency space and the importance of robust security measures to safeguard users’ assets. As the industry continues to evolve, exchanges must remain vigilant and proactive in addressing potential threats to maintain trust and security within the community.

Source link

Latest articles

Anubis Ransomware Now Hitting Android and Windows Devices

 A sophisticated new ransomware threat has emerged from the cybercriminal underground, presenting a...

Real Enough to Fool You: The Evolution of Deepfakes

Not long ago, deepfakes were digital curiosities – convincing to some, glitchy to...

What Happened and Why It Matters

In June 2025, Albania once again found itself under a digital siege—this time,...

Why IT Leaders Must Rethink Backup in the Age of Ransomware

 With IT outages and disruptions escalating, IT teams are shifting their focus beyond...

More like this

Anubis Ransomware Now Hitting Android and Windows Devices

 A sophisticated new ransomware threat has emerged from the cybercriminal underground, presenting a...

Real Enough to Fool You: The Evolution of Deepfakes

Not long ago, deepfakes were digital curiosities – convincing to some, glitchy to...

What Happened and Why It Matters

In June 2025, Albania once again found itself under a digital siege—this time,...