CertiK’s March Report Reveals Biggest Crypto Threats As Kraken User Loses $18.2M
The post CertiK’s March Report Reveals Biggest Crypto Threats as Kraken User Loses $18.2M appeared first on Coinpedia Fintech News
CertiK’s March 2026 security report confirms $59,509,931 lost to exploits, phishing, and scams – with just $21,912 returned. That is a recovery rate of 0.04%.
Wallet compromise led all categories at $26,846,293, followed closely by phishing at $21,408,097. Together the two account for over 80% of March’s total losses. By attack type, DeFi protocols suffered the most at $32.8M, followed by social engineering at $18M.
The single largest exploit was Resolv, which lost $26,846,293 to a wallet compromise.
Q1 2026 Closed With $501M Across 145 Incidents
Zooming out, Q1 2026 closed with $501M in confirmed losses across 145 incidents per CertiK. That figure represents a significant drop from Q1 2025’s $1.67B, though the comparison requires context. Last year’s total was heavily distorted by the $1.4B Bybit hack.
Excluding that single incident, the quarter-on-quarter improvement looks considerably less reassuring.
Also Read: Bitcoin Monthly Close: 5 Months In the Red, But Bulls Are Watching THIS Signal
The Hack That Closed the Quarter
As the report dropped, a live incident was already unfolding. An unknown Kraken user lost $18.2M in a suspected social engineering attack, with the threat actor bridging stolen funds from Ethereum to Bitcoin via THORChain. The incident was flagged by on-chain investigator ZachXBT.
The Kraken victim was not compromised through a technical exploit. According to ZachXBT, the attacker used social engineering to manipulate the user into surrendering access to their funds.
THORChain and the Biggest Thefts of 2026
The Kraken attacker is routing stolen funds through THORChain, the decentralised cross-chain protocol that has appeared repeatedly as the laundering route of choice in major 2026 thefts. THORChain is permissionless by design, which means there is no mechanism to freeze or intercept funds once they are in motion.
Social engineering has replaced code exploits as the dominant attack vector in 2026. The Kraken incident is a direct illustration of that shift.
Never Miss a Beat in the Crypto World!
Stay ahead with breaking news, expert analysis, and real-time updates on the latest trends in Bitcoin, altcoins, DeFi, NFTs, and more.
Subscribe to News FAQs How can crypto users protect themselves from wallet compromises and phishing?
Users should enable hardware wallets, multi-factor authentication, and verify all communications to prevent social engineering and unauthorized access.
What are the broader implications of rising social engineering attacks in crypto?
As social engineering overtakes technical exploits, investors may face higher personal risk, increasing demand for user education and security-focused services.
Who is most vulnerable to crypto social engineering attacks?
Individual users and smaller DeFi participants are most at risk, as attackers exploit human error rather than weaknesses in blockchain code.
🧐🤓 În această dimineață am stat cu $SIGN Protocol pentru puțin timp, și este mai complex decât majoritatea sistemelor de airdrop despre care oamenii vorbesc casual. 😂 Distribuția multi-chain nu este doar despre trimiterea de token-uri peste tot, ci despre coordonarea revendicărilor între lanțuri, evitând duplicarea.
i se pare că $sign gestionează acest lucru printr-un sistem de urmărire bazat pe atestare, unde eligibilitatea este înregistrată o singură dată și verificată între rețele, nu reemisă în mod oarbă.
Am analizat integrarea cu sistemele naționale, se simte mai puțin ca un plugin direct și mai mult ca o structură de atestare pe un strat de punte care ar putea fi aliniată cu cadrele de identitate dacă guvernele decid vreodată să interacționeze cu acesta. Asta rămâne un „dacă” mare.
Am continuat să revin la metrici precum atestările active, utilizarea cross-chain și adoptarea de către dezvoltatori, nu doar la numerele brute de utilizatori.
i iată tensiunea: dacă stratul de indexare este compromis, întregul flux de verificare ar putea fi distorsionat. Datele ar putea exista în continuare, dar accesul și ordonarea devin discutabile.
i urmăresc că adevărata întrebare este... poate $SIGN system să rămână de încredere dacă stratul său de citire se defectează?