TGViewer
Libre Blockchain Libre Blockchain @librehash · 2.49K subscribers
Post #30455 444
Libre Blockchain This same vulnerability was identified by Trail of Bits in their audit of the project 'Meson Fi'. Severity = high (for obvious reasons) and this vulnerability was a lot more succinct than the one that's in the Gnosis Safe contracts. 1. They identify two…
If you are a large entity in the crypto sphere and you have a substantial amount of funds stored in a Safe multi-signature contract deployment, I would strongly recommend that you (a) just contract somebody in-house to procure you tailor-made multi-sig solution [especially if you have tens of millions of dollars to throw around...why not invest in better security for your funds?..like huh?] (b) MIGRATE from SAFE CONTRACTS UNTIL THEY FIX THIS ISSUE.

Why Large Entities Using Safe are at Risk

I'm more than certain that WazirX and Bybit were victims of this same attack vector. In both situations we have exchanges carrying hundreds of millions of dollars in Safe smart contracts (multi-sig; upgradeable proxy). Each signature provided for both hacks had a v > 30 (**what a coincidence**) and the signatures were validated against hashes that are ENTIRELY different than what we can see in the transaction log, most stack exec traces or other online visualizers.

We still don't have an official story on the WazirX situation. Remember that one required 4+ signers. Three on the exchange's end that all confirmed (via 3rd-party audit) none of their devices were compromised. Beyond that, the 4th and final signer was an entity called 'Liminal', whose sole duty was to effectively play 'last line of defense' for WazirX in the case that one or more of their signers did end up being compromised somehow. Neither party (Liminal / WazirX) willing to budge on their declaration that neither was operationally compromised in any way, shape or form. No private keys were siphoned or leaked and there is scant (or no) evidence to corroborate the idea that the exchange owners blind signed something foolishly (again, worth noting that they contracted Liminal to serve as that last line of defense in the event they did somehow get compromised or bamboozled into letting a suspicious / weird transaction get signed).

What are the chances that these two exchange hacks weren't due to their respective owners or related custodians being dipshits too lazy to double check before signing off on a transaction from a wallet holding hundreds of millions of their funds despite possessing enough wherewithal and motivation to deploy an extensively secure, clandestine and comprehensive authorization scheme for those same funds? What are the chances that this disease of apathy and carelessness didn't actually afflict every single authorized signer of these two respective exchanges, simultaneously, right when the culprit (Lazarus) had decided to strike?

This exploit/vulnerability likely won't impact smaller users (small in terms of funds), because the risk/reward ratio doesn't justify it. The effort/resource/brain power necessary to pull this off mandates a sizable payout. But when we look at WazirX losing >$250 million and Bybit losing >$1.5 billion (both in the space of less than a year) ...this has been a lucrative ass campaign for Lazarus.
  • 👍 1
More from @librehash
  1. Oct 9, 2026I'm back.
  2. Jun 10, 2026Until an adequate quantum-safe migration plan is proposed with a concrete timeline for imp…
  3. Jun 10, 2026The quantum clock is ticking: it's Bitcoin's problem, not Ethereum's https://www.coindesk.…
  4. Oct 30, 2025Update Regarding the Meeting Between Trump & Xi Jinping in South Korea Trump recently conc…
  5. Oct 17, 2025■□□□□ ℹ️ Data-Leak: Price sheet of 200+ crypto influencers and their wallet addresses from…
  6. Oct 16, 2025DPRK Adopts EtherHiding: Nation-State Malware Hiding on Blockchains. EtherHiding, a novel…
Threads Profile ViewerView any public Threads profile without an account.Open ThreadLook →Writing with AI? Make it sound human.Metric37 rewrites AI drafts so they read naturally. Free AI detector, 1,500 words free.Try Metric37 →