Specter

@vikktorrrre Why not? Be positive

Two accounts you never want to see in your replies

@0x11b6 @DeanEigenmann Crazy.... Not sure there could be any incident that will even cause a debate such debate again

@SpecterAnalyst Yep, even in the crowd when they discussed it at ETHBerlin... IIRC @DeanEigenmann took the other side of the debate just to cause everyone to think, whilst wearing a white bitconnect hat

One of the most infamous incidents in Ethereum history involved the Parity Multisig wallet, in which a total of 544,000 ETH (~$187.3M at the time, now ~$1.4B) was lost or frozen in 2017 On July 18, 2017, about 153K ETH (~$30M) was stolen from three project multisig wallets created via Parity. There was a 13-hour gap after the first wallet was drained before the attacker continued, successfully draining two more projects. White hats identified the same vulnerability and raced to exploit it, managing to secure some funds before the attacker could access them. The attacker distributed ~70K ETH across seven wallets (10K ETH each) and held them for years. Laundering activity began in 2021, with the last visible movements in 2024. The funds moved through services like Tornado Cash and eXch. I traced part of the funds to the Bitcoin network and also identified wallets used to withdraw from Tornado in 2023. The attacker still holds the majority of the stolen funds, totalling 109kETH (~$234M), across the following wallets: 0x4FB0BC75d56035fb6d07C80E44c156C88ba852ba 0x92446EB937Ec98842A146021002f605fDaBbE9D9 0x6a14E385Fff2F21aBE425A07CE29842b7037A80D 0x18345118bd04c405B4D74941563a21B5a2bF06b7 0xEf0683BEF79b7AD85573415c781eDFDE8bEc65b1 0x4De76b3dfD38292Ba71cF2465Ca3a1d526dCB567 0xB3764761E297D6f121e79C32A65829Cd1dDb4D32 The second incident (November 2017) In November 2017, a user known as devops199 accidentally triggered another critical bug. After the July exploit (caused by a function visibility issue), Parity deployed a new wallet library. However, it still contained a flaw. The user became the owner and then self-destructed the contract, effectively deleting the shared library. Since all Parity multisig wallets depended on that library for execution logic, this action permanently froze all affected wallets. Impact: -598 wallets affected ~514K ETH (~$156M at the time, now ~$1.1B) was frozen -Funds are still inaccessible today The largest affected wallet (~60% of total) belonged to the Web3 Foundation, tied to early fundraising for Polkadot Polkadot multisig (306K ETH): 0x3BfC20f0B9aFcAcE800D73D2191166FF16540258 Had the July hack occurred today, a small portion of the stolen funds would likely have been frozen and recovered with AML tools, and investigators would respond much faster and organizations such as @_SEAL_Org now operating in this space. Stay smart

@0x11b6 You were there?

@SpecterAnalyst EIP999 proposal timeline was some interesting times

@Naeven_ Crazy dude 🤣😂 some accounts only need followers to showcase their banger boys talent

@c0de4c0ffee @VitalikButerin 🤣🤣 that's my 🐐 please

@SpecterAnalyst I believe @VitalikButerin is devops199🫣

@inversebrah Everythingcrypto[.]com

we take wat we can

@zachxbt @evilcos @coinbase @im23pds And with the numbers of CC out there.. Coinbase is crazy

@evilcos @coinbase @im23pds So basically Coinbase has an official page live threat actors can use to target Coinbase users via seed phrase social engineering if they wanted?

我很疑惑 Coinbase 为什么会有这样的页面，直接让用户输入明文助记词做资产恢复？如此不安全的行为，匪夷所思…@coinbase 我都差点以为子域名被黑了…cc @im23pds withdraw.commerce.coinbase.com/seed-phrase

@tradexyz This is big W

S&P Dow Jones Indices and trade[XYZ] have joined forces to launch the first official S&P 500 perpetual contract, available exclusively on Hyperliquid. For 69 years, the S&P 500 has been a defining reference point for global finance. Until now, access to that benchmark has been shaped by market hours, intermediaries, and geography. Today, that changes. The S&P 500 perp is now available 24/7/365, anchored by the official index data required for deep liquidity and institutional confidence at scale.  SPDJI helped define modern indexing. They are stewards of an iconic benchmark, the standard against which portfolios across the globe are measured. We are honored to bring that legacy on-chain. Trade[XYZ] is bringing the world's most iconic assets towards a future of global, continuous markets — a future powered by Hyperliquid.

@tanuki42_ @VenusProtocol Community raised an alarm before the incident bit the team said "everything looks ok"

@SpecterAnalyst @VenusProtocol 🙃

You can lead a horse to water @VenusProtocol... 🐴 Venus was notified months in advance by multiple parties about this exact risk and chose to do nothing. I hope any users affected get fully reimbursed.

@zachxbt @WazzCrypto The quotes are sponsored

@WazzCrypto ???

Other than Eric Trump (who is barely sentient), there's not a single comment from a real person on this post It's all bots

Most people just want to post for engagement. For example, look at the $5M swap incident a few days ago everyone posted the same information with no details except mine (I'm the second to post it on X using timing). When it was later attributed, I was also the first to make the attribution with well detailed analysis. Most accounts simply just put the attribution, except Lookonchain, which also added some details. You sure understand why now.

@Naeven_ You can't blame lookonchan.. they didn't just wait longer to know what exactly the funds is meant for Patient is very important. Assumption kills and details matters

@badattrading_ You should be familiar

bro didn't like me showing his bundles

@blockaid_ @VenusProtocol Venus and exploits 🤝

🚨Community Alert: Blockaid exploit detection system detected an ongoing exploit affecting @VenusProtocol via delegated borrowing abuse. Example exploit tx: bscscan.com/tx/0x5aede60c7…. Please pause any Venus interactions, avoid signing delegation approvals, and revoke existing delegate permissions immediately.

@Nikopolos I remember that day. I was totally shocked and surprised at the same time. The amount was just too big to lose to such an attack.

This $50M case that @SpecterAnalyst flagged early on became the single largest confirmed payoff in my dataset and part of a broader pattern where address poisoning losses hit $63M in two months after Fusaka, a 13x increase over the pre-upgrade period. sergeenkov.com/fusaka-poison-…

Lol, imagine trying to justify one wrong by pointing to another. Undisclosed ads will always be treated the same whether the post was made before, now, or three years ago. It’s like saying illicit activity shouldn’t be uncovered just because it happened a long time ago. I remember linking some Meteora campaign payments that you were involved in, which weren’t disclosed the same goes for other influencers. Your followers should be your responsibility, not a way to get rich off them.

CT showing how incapable they are of identifying organic vs astroturfed engagement by accusing Mr Wonderful of undisclosed ads while ignoring the 99% of CT people who have been running undisclosed promos with botted engagement for the last 5 years. lol, lmao even

The wallet is linked to the 10/11 whale, which was confirmed by @GarrettBullish to be his client. Wallet 0xcaE1 received $2.6M from Kraken between October and December 2025. On December 20, $2M was deposited to Binance. The deposit address had previously received 100M $USD1 on November 17 from: 0xF6FD12fbf8bBe0e08Ac739c3634CD1cB21acf5E9 Wallet 0xF6FD1 was first funded with 70.4K ETH (~$331M) on August 23, 2025 by: 0x079433Ee99C5dF344Fa9836c8cc6F64E6c4859b6 The funds were withdrawn from Hyperunit to 0x079. Tracing further, the source of the funds leads to: 19D5J8c59P2bAkWKvxSYw8scD3KUNWoZ1C Which links us to the main source: 1KAt6STtisWMMVo5XGdos9P7DBNNsFfjx7