Twitxy Saved

Pluto 🚢

Verified account This account is verified. Learn more

@pluto_hbr

Building @Harbor_DEX
Joined November 2021
133 Following 7.5K Followers 950 Posts

Latest posts 5

Pluto 🚢 Verified account @pluto_hbr
> Engineer A from Wallet DevOps downloaded a tampered Homebrew installation in order to install a popular AI coding tool after searching for it on a search engine.

> The attacker soon discovered Wallet DevOps Engineer A had a container deployment permission token on his computer.

"I don't always hold deployer keys to billion-dollar MPC infrastructure on my dev laptop, but when I do, I pipe curl to bash to install agentic coding tools."
Binance @binance Nov 3
View quoted post on X
1 replies 0 reposts 11 likes 1.7K views View on X
Pluto 🚢 Verified account @pluto_hbr
The latest TC release 3.18 was done as a private binary (something we had done before when patching crits). There was a long-standing practice that if a node requested, by signing a message with their validator key, devs would send them the validator-key encrypted diff of the security patch. That’s exactly what the malicious node did in this case. It’s possible even that the private release spooked them into speeding up their timeline for the attack. I find this class of attack very interesting. Networks need to be designed maximally defensive, even against their own validators. In this case, a malicious validator can still get the source code for patches and exploit them before the code goes out. I wonder if this puts an end to that practice. It all exists on a spectrum of decentralization. I actually don’t disagree with @jpthor that closed source TSS might be the move from here. Anyone who is saying that’s “the end of the experiment” is either a crypto-anarchistic maxi that lost the plot or an NK hacker astro-turfing protocols into not making sound trade-offs between security and decentralization.
6 replies 5 reposts 49 likes 15K views View on X