0 sats \ 9 replies \ @cryptocoin OP 3 Aug 2022 \ on: 🧵Widespread Solana exploit draining wallets throughout the ecosystem 🚩🚩 bitcoin
https://twitter.com/phantom/status/1554626111535026177
https://nitter.it/phantom/status/1554626111535026177 <-- Shows the thread in a single, easy-to-read, web page
1/2Hmm Solana hack seems to:-Not be via program(contract) -Have hit a few wallets, but not many major ones -Not just be PhantomMy best first guess would be some sort of shared library had a malicious update that is letting the tx sign once a wallet is unlocked.
https://twitter.com/adamscochran/status/1554628443878350851
https://nitter.it/adamscochran/status/1554628443878350851 <-- Shows the thread in a single, easy-to-read, web page
reply
I can’t believe I’m sending my fund from a “non-custodial” wallet to my exchange account just to protect it. Good job #Solana 🤦🏻🤦🏻🤦🏻
reply
There's also been evidence of this issue affecting ETH users, although it seems less widespread.
reply
There's an ongoing attack targeting the Solana ecosystem right now. 7000+ wallets affected, and rising at 20/min. Because it's very early and the attack is ongoing, there's a lot of misinformation and speculation. So here are a few thoughts and clarifications.
reply
So far more than 8000 wallets and ~$580M were stolen by the following 4 addresses.[...]
reply
This Tweet kicks off a thread where he tries to narrow it down to two reasons:
So this wallets being drained are all closed source software.Classic.
reply
This Tweet kicks off a thread with a summary so-far:
Seeing a lot of speculation on the hack still. After helping coordinate a SOL Security room for the last 12+ hours and speaking to multiple wallet peoviders, here are some things for the public to keep in mind. Core to everything: we do not have a clear explanation yet. Now, a 🧵
reply
[UPDATE from Solana]
This exploit was isolated to one wallet on Solana, and hardware wallets used by Slope remain secure.While the details of exactly how this occurred are still under investigation, but private key information was inadvertently transmitted to an application monitoring service. 2/3