Tranche Vault on Avalanche Drained of 1.01 Million USDC
Published Updated 4 new reports since it was first published
A Tranche Vault and a TranchePool on Avalanche were both reported drained in separate incidents tied to USDC. One account points to a flash-loan exploit, while another describes a settlement flaw that let a scheduled principal payment be counted twice.
What this rests on
What it means
Tranche vaults and tranche pools sit at the point where onchain lending, structured credit, and stablecoin accounting meet, so a fault in either the share model or the settlement logic can put the underlying USDC flow at risk. Avalanche is the chain named in both incidents, and the stories center on the mechanics of how tranche claims are recorded and redeemed. A flash loan and a day-rollover settlement check are different failure modes, but both are about whether the contract’s internal bookkeeping matches the assets it is supposed to hold.
For builders using these designs, the immediate practical issue is that redemption and payment logic has to survive manipulation at the contract level, not just market volatility. A vault linked to Fence Finance and Valinor Digital was described as exploited on 2026-10-28, and a separate TranchePool incident on Avalanche was described as paying out USDC twice after a rollover check. That means project teams need to review how principal payments, share minting, and settlement timestamps are handled before users rely on them again.
The larger trade-off is that DeFi credit products promise automated settlement and composability, yet they also turn small accounting assumptions into direct loss events. Tranche structures are meant to slice risk and payment streams, but these incidents show how quickly the design can shift from credit plumbing to a single point of failure if the contract rules are wrong. When a vault balance can be emptied or a payment can be counted twice, the gap between financial engineering and software correctness becomes the central risk. (per thecryptoguardian.com)
Still unknown is whether the affected contracts share code, operational controls, or only the same chain and product type. The public details do not say how the identified vault or pool was configured, whether user funds were recovered, or whether the teams changed the contracts after the incidents. What would settle that is a postmortem from the operators of Fence Finance, Valinor Digital, or the TranchePool project, along with any onchain transaction tracing that shows where the USDC moved next.
Market reaction
The move was larger before the first headline than after. That is an observation, not an explanation: the market also moves on things nobody publishes.
How the story was built
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 |
|---|---|---|
| 3 months ago | Oraichain · Unbacked Cross-Chain Mint incident | $1M |
| 11 months ago | US Permissionless Dollar incident | $1M |
| 12 months ago | Moonwell incident | $1M |
| 1.8 years ago | FEG incident | $1M |
| 2.0 years ago | CompoundFork incident | $1M |
4241 incidents stored · 917 were as large as this one or larger ($1M)