Something felt off with Dusk's bridge infrastructure last week, and it wasn't the ZK tech it was a plain old wallet compromise.
On August 16, Dusk's monitoring flagged unusual behavior tied to a team-managed wallet used in bridge operations. Per the official incident notice, they disabled and recycled the related addresses, paused bridge services, and pushed a Web Wallet recipient blocklist. They also said they coordinated directly with Binance after tracing part of the flow onto the exchange.
What made me dig deeper: the notice is oddly specific that only "a small number of transactions" occurred in the window, but it doesn't publish the wallet address, tx hashes, or the amount involved — so there's no way to independently trace the flow on an explorer, which is unusual for a team that otherwise pushes transparency (DuskScan launched just weeks earlier).
Observed: a team-managed bridge wallet was compromised or behaved abnormally, bridge services paused, no confirmed user losses stated.
Interpretation: operational key management, not a protocol flaw but that's the team's framing, not something I could verify independently.
What I can't confirm: exact amount moved, destination wallets, or whether "no losses" holds up after a fuller review.
Anyone tracking the actual flagged wallet on-chain, or is everyone just taking the notice at face value?
@Dusk $DUSK #dusk
On August 16, Dusk's monitoring flagged unusual behavior tied to a team-managed wallet used in bridge operations. Per the official incident notice, they disabled and recycled the related addresses, paused bridge services, and pushed a Web Wallet recipient blocklist. They also said they coordinated directly with Binance after tracing part of the flow onto the exchange.
What made me dig deeper: the notice is oddly specific that only "a small number of transactions" occurred in the window, but it doesn't publish the wallet address, tx hashes, or the amount involved — so there's no way to independently trace the flow on an explorer, which is unusual for a team that otherwise pushes transparency (DuskScan launched just weeks earlier).
Observed: a team-managed bridge wallet was compromised or behaved abnormally, bridge services paused, no confirmed user losses stated.
Interpretation: operational key management, not a protocol flaw but that's the team's framing, not something I could verify independently.
What I can't confirm: exact amount moved, destination wallets, or whether "no losses" holds up after a fuller review.
Anyone tracking the actual flagged wallet on-chain, or is everyone just taking the notice at face value?
@Dusk $DUSK #dusk