Ethereum

Safe{Wallet} frontend infrastructure was compromised.

🥁 We need to reduce our dependence on centralized frontends!

We need more independent frontends implementations or, better yet, generative frontends. At least one signer should use a different frontend.

Bybit Hack Forensics Report
As promised, here are the preliminary reports of the hack conducted by @sygnia_labs and @Verichains 
Screenshotted the conclusion and here is the link to the full report: https://t.co/3hcqkXLN5U https://t.co/tlZK2B3jIW

Ben Zhou

Safe{Wallet} frontend infrastructure was compromised.

🥁 We need to reduce our dependence on centralized frontends!

We need more independent frontends implementations or, better yet, generative frontends. At least one signer should use a different frontend.
https://x.com/benbybit/status/1894768736084885929

A doodler and computerer. I like permissive/permissionless open source, smart contracts, p2p systems, room-scale VR, and NixOS.

shazow.net

Currently: WhatsABI

Safe does have a local client, that presumably you should be using if you're moving $1B+, not the web interface

Software Engineer @ Cadence Design Systems. B4: Stanford EE / Illinois ECE

I was thinking of this, which is now depreciated. Perhaps an APK of the gnosis safe monorepo would also work?

Which are you referring to?

I'd argue that no single client is safe for high value vaults, there should be client diversity in the signing set itself.

In fact the official frontend should actively encourage use of an alternate frontend for at least one signer.