asenderling.eth (@asenderlingeth) header
asenderling.eth (@asenderlingeth) profile picture

More active on Farcaster than here. CB employee (Unit-0x), personal account

United States
Joined August 2023
Photo by asenderling.eth (@asenderlingeth)Photo by asenderling.eth (@asenderlingeth)Photo by asenderling.eth (@asenderlingeth)Photo by asenderling.eth (@asenderlingeth)Photo by asenderling.eth (@asenderlingeth)Photo by asenderling.eth (@asenderlingeth)Photo by asenderling.eth (@asenderlingeth)Photo by asenderling.eth (@asenderlingeth)Photo by asenderling.eth (@asenderlingeth)Photo by asenderling.eth (@asenderlingeth)
Google has been serving malicious domains via suggested results for years. Will this finally be enough attention on it to get them to do something?
1
21
asenderling.eth retweeted
Some learning lessons / recs from @binance hack to crypto teams mixed with my own personal ramblings. - Work devices are for work, personal devices are for personal. No exceptions. - Never install or perform actions on a destination site from a search result. Google is notorious for shitty ad control policies in cases even displaying the legit domain -> then redirect to a malicious copy - Software MUST come from approved channels, nowhere else. Your engineers will be annoyed but whitelisitng apps, extensions, cli tools / binaries, etc is a MUST in today's environment. - Educate your employees and yourself on DPRK attack vectors!!! Every single employee entering your organization must be aware of the common DPRK attack vectors (meeting phishing, contagious interview, pollinrider tactics, etc.). - Never clone / open a repo locally on your machine. Goes without saying but this a tried and true payload delivery mechanism for DPRK - Use a freaking MDM to manage software it's 2026 (probs jamf or iru). One of the compromised engineer's got one of his Homebrew tools (pyenv) with a version that gave the attacker remote access. Use MDM to manage verified install channels for binaries and anything else. Push config changes (e.g VS Code task abuse), governance for AI tool usage, hunt across your fleet for vulnerable software, auto-updates, allowlists for app installations, execution allowlisting for binaries, etc. - Only dedicated devices + dedicated accounts should have access to critical / existential actions. We've been doing this at Monad for a while and encourage eco teams to do the same. - Make a threat model pls. In the words of @iphelix what are your crown jewels? You must know what are the existential threats to your company and defend them / build the controls so that even if you ARE compromised - it doesn't destroy you. - Use an EDR (Crowdstrike or Huntress if smaller and need something more managed) and build custom IOAs based on threat intel (e.g this binance post-mortem). EDR did NOT detect for Binance - it doens't mean that's the case for you - write some damn custom detection rulesets. - Egress controls on every device. Yes i know people don't like Zscaler but your employees are going to fall for the B-team tactics time and time again. Block newly registered domains by default and setup some automation to keep adding new IOCs from your threat intel. - Speaking of threat intel - do you have any??? If you don't rss feeds are ok - X tho is really the gold mine you should setup custom detection feeds based on your organization's threat model. Otherwise can use cve.[now], cloudlfare zero-wire, and @_SEAL_Org threat intel as a basic starter. A lot of rss feeds are poop so focus on quality. - No long-lived sessions or tokens on laptops. Short-lived, scoped, device-bound creds. Simple enough but hard to apply across the org. - Yubikeys won't save you from malware. This is not the only line of defense but for phishing yes they're great so obv have them. - Vendor risk is literally sky-high rn. You cannot allow employees or yourself to blindly install / run / grant perms to 3rd party platforms. Distrust by default and Oauth grants (hey google workspace admins i'm talking to you) should be set to read-only for ALL apps by default. If you rmr this is how Vercel got pwned. - Signing policy should be enforced no matter who's calling. Destination allowlists, per-tx and velocity limits, hard block on EIP-7702 from hot wallets. - Detection and alerting do you have any??? The attackers were incubating since JUNE - months of time to prep for lateral movement until they could escalate. How do you know you're compromised or behavior is suspicious? - lastly just going to leave this here: xitter.gq/alpeh_v/status/2116172…
Frog put the keys in the HSM. "There" he said "now we cannot leak the private key". "But our servers can ask the box to sign with the key" said Toad. "that is true" said Frog
2
8
4
36
2,429
I stg if they try to reinvent the wheel instead of pouring money into an org that's already demonstrated immense success and devotion to the space I will give up on the rest of the industry.
2
18
asenderling.eth retweeted
Um, hello.
IS THERE AN INDUSTRY SECURITY ALLIANCE COMING? @cz_binance told us on @_TalkingTokens he wants to help form an industry security alliance to "share the best practices, cross audits, help each other freeze funds very quickly." Amid the latest hacks and AI's rapid evolution - security is top of mind right now for everyone. "Given what's happened in the last few months, I think this will come together pretty quickly."
11
21
1
192
8,271
asenderling.eth retweeted
Replying to @paoloardoino
Thanks to @SEAL_911 🙏
4
14
832
asenderling.eth retweeted
Replying to @FDLabsHQ
@FDLabsHQ Please can you freeze the $3.45M FDUSD held at 0x5227f603c1ee34ce3c06efe6477003bdfccb2f8c It's assets stolen from Binance and I don't have a contact to reach you.
1
5
2
32
4,642
asenderling.eth retweeted
1/ If you got tagged in a Hyperliquid “Season 2 HYPE vote” post today, don’t click it. New drainer lure that's coming up a bunch, they literally just tagged me in it. The “mass ping” method...:
3
3
18
1,285
asenderling.eth retweeted
The usual suspects create the lie, the usual suspects push the lie, the usual sheep believe the lie. The MAGA cult is a cesspool of lies.
216
1,623
31
13,575
133,305
asenderling.eth retweeted
only OG's know
4
3
37
713
asenderling.eth retweeted
If you were just drained to any of the following addresses, please can you reach out to @SEAL_911 asap. Total loss is >$72M+ and increasing. TK6DWNpNe1w2iJRNFpU8aHdrPTATxvXT6C TBkcUMYC7CkTK99tkTnaStQVBastfrs9d9 TCGE3xp6YGRKXxDZiLfysgJW3f22KfMNsW TSDWtuZ2pARUVz4v3PkL2hi3iXPjowAr5a bc1qjqgwejnp8dc0x2938x9n9954hj97t82unx49dl 0x83aeac166f6832ae3500000a24510a95a052a599 0x033636e45d519bebb7b5c2520ca6ce56fbdb4f7a 0x69c8f401cfc6cd40ac94691d6d7c48e3b7a47841
34
64
29
395
213,245
asenderling.eth retweeted
🚨 Please get in contact with us ASAP if your funds were drained to these addresses. @SEAL_911 Telegram: [@]seal_911_bot
If you were just drained to any of the following addresses, please can you reach out to @SEAL_911 asap. Total loss is >$72M+ and increasing. TK6DWNpNe1w2iJRNFpU8aHdrPTATxvXT6C TBkcUMYC7CkTK99tkTnaStQVBastfrs9d9 TCGE3xp6YGRKXxDZiLfysgJW3f22KfMNsW TSDWtuZ2pARUVz4v3PkL2hi3iXPjowAr5a bc1qjqgwejnp8dc0x2938x9n9954hj97t82unx49dl 0x83aeac166f6832ae3500000a24510a95a052a599 0x033636e45d519bebb7b5c2520ca6ce56fbdb4f7a 0x69c8f401cfc6cd40ac94691d6d7c48e3b7a47841
5
26
2
83
18,100
asenderling.eth retweeted
I wasn’t going to comment since this is a really bad take IMO, but since it’s taken off I feel the need to. To my understanding, there is no evidence whatsoever pointing to a break of decades old hardness assumptions like elliptic curve cryptography. 1/n
Today I call upon the blockchain industry to calmly begin planning for "bunker mode". My personal recommendation is to set in motion a controlled mass migration of assets to fresh addresses, i.e. addresses whose pubkeys remain hidden behind a hash. Holders, starting with large and sophisticated ones, should consider moving the bulk of their funds to addresses that have never signed a transaction. And when they do sign one, they should also move remaining funds to a new address (possibly generated from the same seed phrase). Don't rush. While I believe there is cause for action a rushed migration would do more harm than good. Don't panic either. Moving assets to protected addresses is a simple, preventative step which does not require new cryptography or new wallets. IMO it is now reasonable to brace for the possibility that ECDSA breaks before qday, in the worst case in months not years. By "break" I mean fast private key recovery (e.g. in one week) on available hardware (e.g. a large GPU cluster). Recent days have been humbling for human mathematical intuition. Long-held, unquestioned hypotheses have fallen. This includes the n log(n) bound for integer multiplication and the 3SUM conjecture. In hindsight, May's unexpected disproof of the Erdős unit distance conjecture was our warning shot. Yesterday's OpenAI drop made it clear that mathematical superintelligence is upon us. They say there are weeks where decades happen. We are about to live through weeks where centuries of mathematical progress happen. Could our magic 64-byte ECDSA signatures be too good to be true? Was it just security through obscurity all this time? Elliptic curves feel especially vulnerable to superintelligence. Curves carry rich structure, with room for fancy tricks like Schoof, Frobenius, pairings. (By contrast, hashes are designed to minimise algebraic structure.) Separately, as Ewin Tang can attest, an efficient quantum algorithm sometimes foreshadows an efficient classical one. We should be open to the possibility of a classical counterpart to Shor that breaks elliptic curves and RSA at once. Also noteworthy is the striking under-representation of cryptographic breakthroughs among the 722 mathematical results OpenAI published. I've witnessed first-hand the US government censoring academic quantum cryptanalysis results. Backroom interventionism is my base case. I urge large, sophisticated actors to lead by example. Project11's "risq list" (bitcoin-risq-list.projecteleven[.]com) is a great tracker of exposed BTC pubkeys. Binance, Bitbank, Robinhood, Bitfinex, and Tether have an opportunity to harden their cold storage. Next month I'll address institutions in London in a live Q&A (forum.ethereuminstitutional[.]org/london-2026). Again, please do not rush. Wallets holding under 50 BTC enjoy partial cover from "Satoshi's shield", i.e. his 20K exposed addresses that hold 50 BTC each. Load-bearing signers like oracles and L2 security councils should consider rotating ECDSA pubkeys with every signed message and/or multi-signing with a hash-based schemes like SPHINCS. Exiting bunker mode safely will require post-AI cryptography. My inclination is to go all-in on hash-based cryptography and avoid structured mathematical assumptions entirely, whether from curves, lattices, or isogenies. A single battle-tested hash (e.g. from the SHA or BLAKE families) yields plausible post-AI security. The Ethereum roadmap on strawmap[.]org fully embraces hash-based cryptography with end-to-end formal verification as a response to the quantum threat. Those timelines must now be revisited and accelerated in light of mathematical superintelligence. I'll be pushing for maximum defensive acceleration.
82
394
99
2,251
360,348
asenderling.eth retweeted
This overlap is legit, here is the map. Somewhat ironically it overlaps on accounts being used to launder funds through Bitget's own cross-chain bridge 🫠🫠🫠
Regarding who is behind the hack: I present to you THE LAZARUS GROUP. just linked this hack to the AFX hack, which stole $24M in July and was specifically attributed to TraderTraitor. The stolen XRP from Bitget was bridged and can be directly linked to the funds stolen in the AFX hack. Stay smart.
3
5
41
5,440
asenderling.eth retweeted
If you are a person or company who has lost crypto, one of the first things that any reputable incident responder is going to tell you to do is to call the police. Except it seems like too few people in crypto know who to call. Here is a list: pangolinintelligence.com/rep…
4
13
2
91
19,812
asenderling.eth retweeted
> Guy who promoted Iggy Azalea Coin, Davido Coin, Jason Derulo coin, Trippie Redd coin, Trump coin, but draws the moral line at Hunter Biden coin
69
94
15
1,555
97,935
Nearly every celebrity foray into crypto is grifting, but if you don't even have 1% of the energy for the Trump family as you do for Hunter you're just a partisan npc
4
41
Hunter's cardinal sin is not paying the right sleazy backroom guys and giving them and their harems of kols the allocation needed to get them to shill. The Trump's, being good little grifters, are deeply connected to these people.
3
35
midwits on ct be like "omg I can't believe a permissionless chain is letting someone I don't like (for totally legit good reasons I promise 😉) deploy a token"
2
31
This you? Only cool with pumping your own team's bags? xitter.gq/MarketBubble/status/20…
We had an interview with Hunter Biden lined up for this Thursday, makes sense now why they reached out. Needless to say we are CANCELING IT.
1
42