#dusk $DUSK @Dusk Network paused its bridge again on August 16… same wallet-flagging playbook as January's incident, almost word for word. That's the part that got me during this CreatorPad dig not the pause itself, but how identical the two incident notices read.
both times suspicious activity on a team managed wallet, addresses disabled and recycled, coordination with Binance after part of the flow touched their platform, "
no user funds impacted. Bridge closed again until a security review wraps, this time folded into the DuskEVM launch prep.
a repeat playbook isn't automatically bad. It means the response is rehearsed, which is good. But it also means whatever hardening happened after January didn't close the actual gap it was the same vector, not a new one. Grabbed my notes from the first incident just to double check I wasn't misremembering. I wasn't.
the bridge's security posture and more about what temporarily paused actually means operationally when it's happened twice in seven months is there a real fix in motion, or just a faster response clock each time?
both times suspicious activity on a team managed wallet, addresses disabled and recycled, coordination with Binance after part of the flow touched their platform, "
no user funds impacted. Bridge closed again until a security review wraps, this time folded into the DuskEVM launch prep.
a repeat playbook isn't automatically bad. It means the response is rehearsed, which is good. But it also means whatever hardening happened after January didn't close the actual gap it was the same vector, not a new one. Grabbed my notes from the first incident just to double check I wasn't misremembering. I wasn't.
the bridge's security posture and more about what temporarily paused actually means operationally when it's happened twice in seven months is there a real fix in motion, or just a faster response clock each time?
