Bhavya Gor | bhavyagor.eth (@bhavya_gor) header
Bhavya Gor | bhavyagor.eth (@bhavya_gor) profile picture

obsessed with winning | prev: @fwdresearch,@earnfirstdollar

onchain
Joined June 2018
Photo by Bhavya Gor | bhavyagor.eth (@bhavya_gor)Photo by Bhavya Gor | bhavyagor.eth (@bhavya_gor)Photo by Bhavya Gor | bhavyagor.eth (@bhavya_gor)Photo by Bhavya Gor | bhavyagor.eth (@bhavya_gor)Photo by Bhavya Gor | bhavyagor.eth (@bhavya_gor)Photo by Bhavya Gor | bhavyagor.eth (@bhavya_gor)Photo by Bhavya Gor | bhavyagor.eth (@bhavya_gor)Photo by Bhavya Gor | bhavyagor.eth (@bhavya_gor)Photo by Bhavya Gor | bhavyagor.eth (@bhavya_gor)Photo by Bhavya Gor | bhavyagor.eth (@bhavya_gor)
got drained in the fluidkey hack yesterday as an engineer I couldn't not dig into how it happened ~$1.6M+ gone across 7 chains in about 25 minutes. most of it already through tornado cash. was it a contract bug? no. every drain went through fluidkey's own relayer, with valid owner signatures. the attacker didn't break anything. they signed as us. and it stopped the exact minute fluidkey took their servers down. so how did they get the keys? my guesses: - a copy of the keys stored somewhere on fluidkey's side - keys that could be rebuilt from data fluidkey held - a tampered web app or code package that leaked keys when people logged in waiting on the post-mortem.
Update on today’s security incident: there have been no unauthorized transactions since 18:05 UTC, when we took all services offline. We are working with SEAL 911 on the investigation and on tracing the funds, and will publish a full post-mortem once it is complete. As a precaution, the web app and all APIs remain paused until our review is complete. We will share further updates on this channel and in individual support chats.
25
8
7
102
17,291
i genuinely dont think the transactions happened when users opened the app it was already done before i opened the ap i had taken a screenshot 1 yesterday - the time on my app when i logged in was 11:26PM the second screenshot is today - i checked the tx time - its 11:08 PM
Fluidkey is back online with v1.79.22 on web, iOS and Android. Previous versions will remain offline. To re-enable transactions on the app go to Settings > Update. We have implemented a block for all previous versions of the web and mobile app, so you will only be able to transact after the update to the safe new version. The attacker used flaws in a third-party logging tool to obtain session data, prepare unauthorized transfers on our servers, and have them signed when a user opened the app. Transfers can no longer be prepared this way in v1.79.22, which also includes additional safeguards. The private keys controlling user funds never left the device. Next, we will be reaching out to affected users individually and publish a full post-mortem.
1
1
24
funds not yet moved (suspected) ETH 0x5864fad453c9f1ef5d0d2a03e7f2589aa847aa7b ~5.5 WETH + 1 ETH (ETH + Base) 0x748ad9c1a4008c00ce14c23d7413c6165f6f7ccb 6k USDC + 747 USDT (Polygon) 0xe02e1a874a182d35283a2ecfd4b80a8e80725c39 5.4k USDC + 0.5 ETH 0xb636ccaa02b4d853dfcd7655dd30e5aff2c66a5b 300 USDT Base 0x48ca547527ed440ed29e3109bf4ade11dbfa9e2a 0.1 cbBTC 0x5230d70bd67458ccbd8ad9b38ad6e45ee77d4619 0.01 cbBTC Polygon 0xfcc6623e0dc3d992280944e76da84a17b54080dd 741 USDT ~$50k sitting. The USDC/USDT can still be frozen.
got drained in the fluidkey hack yesterday as an engineer I couldn't not dig into how it happened ~$1.6M+ gone across 7 chains in about 25 minutes. most of it already through tornado cash. was it a contract bug? no. every drain went through fluidkey's own relayer, with valid owner signatures. the attacker didn't break anything. they signed as us. and it stopped the exact minute fluidkey took their servers down. so how did they get the keys? my guesses: - a copy of the keys stored somewhere on fluidkey's side - keys that could be rebuilt from data fluidkey held - a tampered web app or code package that leaked keys when people logged in waiting on the post-mortem.
3
7
818
(some txs) Funded via Tornado 0x81f3c4a6d3f23f707c11a29904daed7610a9494fdc0498ac69367af40de8004f First drain $476k 0x5e76951b25bdcda8aef31e640229a63e1ef3671578461dd7d04eb725d9b1b094 349 ETH to Tornado 0x187f62785fc015fc6def8cb1c2f9b9744d7650ecbc5c4dde22d1440a8531fa29
3
672
1.7M+ is all transactions i could trace (not mine)
1
5
820
can someone help me out - my fluidkey just got wiped and i cant login to my account anymore 😭 @moritz_fluidkey @fluidkey
6
10
1,771
my fluidkey just got hacked @fluidkey
3
5
926
Bhavya Gor | bhavyagor.eth retweeted
started crypto to retire my bloodline but ended up setting us back 3 generations
83
144
13
2,164
66,308
Bhavya Gor | bhavyagor.eth retweeted
soon 👀
1
4
186
is ethereum:native pegged to who NVIDIA’s CEO is??
151
what if jensen joins anthropic before the IPO?
126
AI taking jobs will work like compound interest. For years it looks like nothing's happening. Then one year it's everything. (2028?)
4
176
Bhavya Gor | bhavyagor.eth retweeted
Building basquet Baskets of tokenized stocks for Stocks Maxxing on @base, available on both mobile and web.
4
2
1
10
559
delhi's aqi is as much as ethereum:native
2
219
DRIP is an ERC-4626 vault share trading on @Uniswap v4. Our custom hook takes a USDC-side fee into the reserve, and its TWAP oracle is an early-warning signal: when DRIP drops, the Risk agent tightens lending.
1
29
And no one can tie a phone to a shop: every chain read goes through Anon-RPC (the Nox mixnet), backed by the @ethereumfndn . ZK proofs hide which pass is yours. Anon-RPC hides which one you asked about. We didnt win any thing, but was a fun ride. @ETHGlobal
16