Security · Analysis
46 Billion Synthetic Bitcoin Converted Into 4.39 Real Ones
Symbiosis's BridgeV2 accepted a message it should have rejected and minted synthetic BTC with nothing behind it. The attacker held more nominal Bitcoin than will ever exist, and got out with about $336,000 — because the mint was never the hard part.
At approximately 04:28 UTC on September 11, Symbiosis found evidence that its Bitcoin bridge was under attack and halted all BTC routing. By then the attacker had already done the impossible-sounding part: minting roughly 262 raw units of syBTC, the synthetic token that is supposed to represent real Bitcoin held in custody elsewhere.
There was no Bitcoin behind any of it. Symbiosis attributed the incident to "inaccurate message validation, which allowed for the malicious minting of synthetic BTC without real collateral backing." DefiLlama filed it under a category that says the same thing in three words: Unbacked Cross-Chain Mint.
The attacker converted a sliver of that holding into 4.39 WBTC on Ethereum, worth roughly $336,000. Everything else stayed where it was minted.
What BridgeV2 was supposed to check
Symbiosis is a cross-chain liquidity protocol built from paired contracts — Portal on the origin side, Synthesis on the destination side — linked by an off-chain relayer network that signs messages using multi-party computation keys. The Synthesis contract mints a synthetic asset when it receives a properly signed message attesting that the real asset was locked.
The entire security model rests on that attestation being checked correctly. There is no collateral ratio to inspect, no oracle to consult, no on-chain proof of the Bitcoin deposit. There is a message, a signature, and a contract's judgement about whether the two justify a mint. Per Cryptopolitan, the attacker used a signed BridgeV2 receive operation that the contract processed incorrectly, bypassing that judgement.
That distinction matters for how the failure should be read. This was not a stolen key or a compromised relayer — nothing reported so far suggests the MPC signing set was breached. It was the receiving contract mishandling a message, which is the more common and more recoverable of the two failures, and also the one an audit is most expected to catch.
Two counts of the same mint
Sources do not agree on how large the mint was, and the disagreement is worth stating rather than averaging away. The Crypto Times, citing security firm Blockaid, puts it at about 46.1 billion syBTC; citing the analyst account DefraudTG, it puts the figure at 368.9 billion syBTC across both chains. The same report notes the two are counting differently — raw units versus token units, and one chain versus the cross-chain total.
Both numbers describe the same event, and both are past the point where the units mean anything. Bitcoin's supply is capped at 21 million. The smaller of the two counts is more than two thousand times every Bitcoin that will ever exist.
Minted versus realized
| Measure | Amount | Source |
|---|---|---|
| Minted, raw units | ≈ 262 | Symbiosis / Cryptopolitan |
| Minted, token count | ≈ 46.1B syBTC | Blockaid, via The Crypto Times |
| Minted, both chains | ≈ 368.9B syBTC | DefraudTG, via The Crypto Times |
| Left unsold on BNB Chain | ≈ 184.5B syBTC | The Crypto Times |
| Actually realized | 4.39 WBTC ≈ $336,000 | Symbiosis, DefiLlama |
Minting was free. Selling was not.
The gap between 46 billion and 4.39 is the most useful thing in this incident, and it is not luck. It is what a synthetic asset's liquidity looks like from the exit side.
Unbacked tokens only become money when somebody buys them, and the only buyers are the pools. Per The Crypto Times, the attacker's realized proceeds came from selling into Uniswap V4 on Ethereum. A pool holds finite reserves of the thing worth having, and the more of a worthless asset you push into it, the less each additional unit returns. Pushing 46 billion tokens through does not produce 46 billion tokens' worth of anything; it produces the pool, minus slippage, and then nothing. Around 184.5 billion syBTC was still sitting unsold on BNB Chain when the routing halt landed.
This is the same arithmetic that separated the nominal and realized figures in the Cosmos EVM drains, where two chains' block-explorer totals exceeded the realized take across all six. A total mint compromise and a modest theft are entirely compatible, and headlines that lead with the mint size are describing the vulnerability rather than the loss.
The bridge had been audited
Symbiosis has said the native BTC bridge was audited by the security firm Decurity, and the protocol maintains a public audit repository with work from Decurity, Zokyo, SlowMist and Omniscia.
That record is worth stating without drawing more from it than it supports. Neither Symbiosis nor Decurity has published the scope of the BTC bridge review, and no public account yet establishes whether the specific message-validation path that failed was in scope, whether the deployed contract matched the reviewed code, or whether the flaw was introduced after the review. "It was audited" and "the audit should have caught this" are separate claims, and only the first is currently supported.
A bounty with a deadline attached
Symbiosis says it has recovered approximately 15 BTC, moved to a multi-signature wallet under the team's control, and that the final loss is still being calculated. It has offered the attacker a white hat bounty of 20% of recovered funds, valid until September 13 — after which, the team says, the same 20% goes to anyone providing information that assists recovery.
BTC routing remains suspended. Symbiosis says other routes, including EVM chains, TRON and TON, along with its Octopools component, are operating normally, and that funds in ETH and stablecoin pools are safe.
The Take
Two things deserve separating here. The engineering failure is serious and the loss is small, and those facts are not in tension — the attacker achieved unlimited minting authority and was defeated by market depth, which is a defence nobody designed and nobody should count on. Had syBTC been deeply liquid, the same bug would have produced a nine-figure story. The second thing is the bounty clock, and this desk has now watched three protocols in three weeks reach for the same instrument. Offering 20% to a thief is a rational trade when the alternative is nothing, but the deadline structure here is new and slightly odd: 20% to the attacker until September 13, then 20% to informants afterwards. That is a negotiation that has stopped pretending to be anything else, which is at least honest. What would be more useful than either is the post-mortem. Symbiosis has named the failure class — inaccurate message validation — and that is more than many teams offer in the first day. The test of this response is whether the specific check that failed, and its relationship to the audited code, shows up in writing once the accounting is done.