Blockaid flags ongoing $3.43 million exploit on K3 Capital’s sBOLD vault
- Published
- Updated
Blockaid identified two separate DeFi exploits affecting K3 Capital and Reental, with losses reported on Ethereum and Polygon. The incidents highlight how exposed vaults and cross-chain DeFi systems remain to security failures.
Key claims & sources
What it means
K3 Capital’s sBOLD vault sits inside the DeFi lending and yield landscape, where smart-contract systems can move value quickly across chains and protocols. Blockaid’s report places the incident on Ethereum and ties it to a broader pattern of security failures that DeFi teams have been trying to manage for years. Reental’s separate Polygon loss in the same coverage shows that these problems are not confined to one network or one product line.
For builders and users, the immediate takeaway is that vaults and connected DeFi services need tighter monitoring, faster response plans, and more careful risk checks before assets are deposited. A protocol that integrates with other systems can inherit weaknesses from those links, and this kind of incident makes that exposure visible. It also puts pressure on teams to harden contracts and review dependencies rather than treating security as a one-time launch task.
Still unknown is the exact path the attacker used in the sBOLD exploit and whether the Reental incident is linked to the same operating pattern. Blockaid’s snapshot does not settle whether additional funds remain at risk or whether recovery steps are underway. Public disclosures from K3 Capital, Reental, or their developers would be needed to pin down the mechanics and the full scope.
Market reaction i
The total crypto market fell 0.3% in the 4 hours after the first headline, after falling 0.4% in the 2 hours before.
34 prices, one every 30 minutes · The move was larger before the first headline than after: an observation, not an explanation. The market also moves on things nobody publishes.
Coverage timeline
Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.
Thefts of a similar size
| When | What happened | Figure |
|---|---|---|
| 5.3 years ago | Punk Protocol · Contract vulnerability incident | $4M |
| 11 months ago | Unleash Protocol · Privilege compromise incident | $3.9M |
| 11 months ago | Flow · Infinite Mint incident | $3.9M |
| 1.5 years ago | ForceBridge · Improper Access Control incident | $3.9M |
| 3.6 years ago | Patricio Worthalter · Phishing attack incident | $3.8M |
4332 incidents stored · 556 were as large as this one or larger ($3.9M)