DeFi Intel

Hedera-Based Bonzo Lend Loses $9 Million in Oracle Exploit

Bonzo Lend, a lending protocol built on the Hedera network, lost $9 million in an exploit involving an oracle. The report is categorized under hacks and exploits news. No further details about the incident are available in the provided text, as the article body contains only page styling code.

TL;DR

On June 6, Alex Protocol on the Stacks blockchain lost about $8.3 million due to a self‑listing verification flaw. The Alex Lab Foundation will fully reimburse users in USDC, highlighting both the security challenges and the protocol’s commitment to restore trust.

Key facts

  • The attacker drained 8.4 million STX, 21.85 sBTC, 149,850 USDC/USDT and 2.8 WBTC.
  • Alex Lab Foundation pledged full USDC reimbursement to affected users.

On June 6, the Bitcoin‑based DeFi platform Alex Protocol suffered a major security breach that resulted in the loss of approximately $8.3 million in digital assets. The exploit, attributed to a flaw in the protocol’s self‑listing verification logic, allowed an attacker to drain liquidity from several pools, siphoning roughly 8.4 million STX, 21.85 sBTC, 149,850 USDC/USDT and 2.8 WBTC. In response, the Alex Lab Foundation announced a structured reimbursement plan in USDC for affected users, promising on‑chain notifications and claim forms within days of the incident.

Background

Alex Protocol operates as a decentralized finance platform on the Stacks blockchain, which extends Bitcoin’s security model to enable smart contracts and DeFi applications. The protocol’s ecosystem includes multiple asset pools that provide liquidity for trading and lending activities, and it relies on a self‑listing verification mechanism to approve new assets for inclusion. Prior to the June 6 breach, Alex Protocol had already experienced a significant exploit in May 2024, when its cross‑chain bridge infrastructure was compromised, resulting in a $4.3 million loss that the team linked to the North Korean Lazarus group. The May incident prompted the protocol to work with blockchain analyst ZachXBT to trace stolen funds, highlighting ongoing security challenges within the platform’s architecture. The recent exploit underscores the continued vulnerability of DeFi protocols that depend on complex verification code and underscores the importance of rigorous auditing and rapid response mechanisms in the rapidly evolving Bitcoin DeFi space.

What happened

According to a Cointelegraph report dated July 11, 2026, the breach on Alex Protocol occurred on June 6 when an attacker exploited a vulnerability in the platform’s self‑listing verification logic. The flaw enabled the attacker to drain liquidity from several asset pools, resulting in the loss of about 8.4 million STX tokens, 21.85 sBTC, 149,850 USDC and USDT combined, and 2.8 WBTC. In an X announcement, Alex Protocol confirmed the breach and detailed the assets taken. The Alex Lab Foundation, which supports the protocol, pledged to fully reimburse affected users using its treasury reserves. Compensation will be issued in USDC, with reimbursement calculations based on average on‑chain exchange rates between 10:00 am UTC and 2:00 pm UTC on the day of the attack. The foundation said wallets affected would receive an on‑chain notification by June 8, along with a personalized claim form to be submitted by June 10. After verification, the team intends to distribute USDC payments within seven days. The report notes that Cointelegraph reached out to Alex Protocol via its X account but did not receive a response before publication. While the technical mechanisms behind the exploit were not disclosed, the protocol indicated a post‑mortem report would follow.

Market impact

The loss of $8.3 million in assets represents one of the largest exploits in the Stacks ecosystem to date, according to the Cointelegraph article. The stolen assets included a mix of native Stacks tokens, wrapped Bitcoin derivatives, and stablecoins, potentially affecting market liquidity across those pairs. The announcement of a full USDC reimbursement by the Alex Lab Foundation may mitigate immediate price pressure on the affected tokens, as users anticipate receiving compensation. However, the breach could also prompt a temporary shift in capital away from Alex Protocol as participants reassess risk, potentially reducing inflows to its liquidity pools. The prior May 2024 exploit of $4.3 million further compounds concerns about the protocol’s security posture, which may influence broader investor sentiment toward Bitcoin‑based DeFi projects on Stacks.

Why it matters

The exploit highlights the persistent security risks inherent in DeFi platforms that rely on complex smart‑contract logic, especially when operating on newer layers like Stacks that extend Bitcoin’s capabilities. The fact that the breach stemmed from a self‑listing verification flaw suggests that onboarding mechanisms can become attack vectors if not rigorously audited. The Alex Lab Foundation’s decision to reimburse users in USDC demonstrates a commitment to maintaining trust, yet the need for such a payout underscores the financial exposure that protocol treasuries can face. Moreover, the incident adds to a pattern of attacks on Alex Protocol, including the May 2024 bridge hack linked to a state‑backed cybercrime group, indicating that the platform may be a recurring target. These developments could influence regulator and investor scrutiny of Bitcoin‑based DeFi, potentially prompting stricter security standards and more robust insurance or reserve requirements across the ecosystem.

DeFi Intel’s take

Editorial analysis, not a statement of fact.

DeFi Intel's take: the Alex Protocol breach suggests that even Bitcoin‑anchored DeFi projects are not immune to the coding oversights that have plagued many Ethereum‑based platforms. The repeated nature of the attacks, first on the bridge and now on asset verification, points to systemic gaps in the protocol’s security audits. While the Alex Lab Foundation’s promise of full USDC reimbursement may preserve short‑term user confidence, the incident could accelerate calls for third‑party audits and insurance solutions within the Stacks community. We read this as a signal that developers need to prioritize formal verification of critical contract pathways, especially those governing asset onboarding and liquidity management, to prevent future losses and sustain growth in Bitcoin‑layer DeFi.

Sources used for this analysis

DeFi Intel wrote this analysis from the reporting above. Any figure or quotation can be checked against those pages.

Frequently asked questions

What caused the Alex Protocol exploit on June 6?

The exploit was caused by a vulnerability in Alex Protocol’s self‑listing verification logic, which allowed an attacker to drain liquidity from several asset pools, according to the Cointelegraph report.

How much did the attacker steal in the June 6 breach?

The attacker siphoned roughly 8.4 million STX, 21.85 sBTC, 149,850 USDC and USDT combined, and 2.8 WBTC, amounting to about $8.3 million in digital assets.

What reimbursement plan did Alex Lab Foundation announce?

Alex Lab Foundation pledged to fully reimburse affected users in USDC, using average on‑chain exchange rates from 10:00 am to 2:00 pm UTC on the attack day, with claim forms to be submitted by June 10 and payments within seven days.

Direct answers

Short answers, written to be quoted.

Will users receive compensation after the Alex Protocol breach?
Yes, the Alex Lab Foundation will fully reimburse affected users in USDC, following a claim process outlined after the breach.
Read full article on Gnews_hacks_exploits →

DeFi Intel is an entity-graph aggregator: we curate, tag and link crypto news to a typed knowledge graph of protocols, tokens, people and incidents. We do not republish the full article body. Use the link above to read the original report at Gnews_hacks_exploits.

Discussion

Comments are reviewed before publication.

No comments yet.

Stay current on entity-tagged crypto news

Get the weekly DeFi Intel brief — entity-graph intelligence covering protocols, tokens and incidents, free to your inbox.