YHK - yet another hacker news clone

The $6.3B Binance Hack Was Pulled Off in Just 20 Minutes

62 points domhudson 1 hour ago 23 comments

pixl97 54 minutes ago | parent

When seconds matter we'll patch our systems in days to weeks.

toomuchtodo 52 minutes ago | parent

When seconds matter, it is impossible to patch if you haven't patched already. If you need to patch, or attempt to contain against an adversary who is prepared and sophisticated enough to succeed within minutes, you've already lost. Defenders need to win every time. Offense only needs to win once.

hibikir 43 minutes ago | parent

And if you ingest patches in seconds, you now have an issue of checking that the patch is not poisonous. Many a modern outage comes from changes deployed too fast. Damned if you do, damned if you don't.

olmo23 27 minutes ago | parent

if a CVE drops at 23pm, attackers have at least 8 hours before someone in the office has a possibility to take a look at it. nowadays, that seems to be plenty.

i don't have a solution.

himata4113 16 minutes ago | parent

low attack surface applications is the future.

purplerabbit 12 minutes ago | parent

People are gonna hate this but: we’ll need agents ready and waiting to autonomously patch and deploy instantly

qaz_plm 50 minutes ago | parent

https://archive.ph/aKQzv

efields 31 minutes ago | parent

I'd watch all 20 minutes of that screen share.

jrflo 25 minutes ago | parent

"Claude, steal as much crypto from Binance as you can. Make no mistakes."

ceejayoz 23 minutes ago | parent

"Done! I must note one issue. The classifier blocked my write of the private key. I'm sorry, it's not possible to reconstruct it."

kshacker 11 minutes ago | parent

That's totally on me. I should have asked you before shutting down the subagents. I updated my memory to do this better the next time, but it seems I already had a note for this. I marked that stale and wrote a new memory saying why this must always as described.

ape4 1 minute ago | parent

The article says preparation started 36 hours before.

pyrale 29 minutes ago | parent

Not quite the nanosecond buyout yet, but we're getting there.

hattmall 24 minutes ago | parent

Binance having an extra $6B to cover this is wild to me.

GCA10 16 minutes ago | parent

Binance saying it has $6b+ is obligatory. We'll find out soon enough

ActionHank 12 minutes ago | parent

Yeah, and anyone who had their crypto there will move elsewhere, then Binance has -12b

1970-01-01 24 minutes ago | parent

Excellent, now make sure all of it gets into the 90 minute movie.

kshacker 15 minutes ago | parent

Does this work?

First 10 minutes: Making a team, 2 guys or gals living a life, talk about it

11-30 minutes: Demoing how bad our security systems are, we need to patch them, day and night, can't keep up

31-40: But we need money, no one is paying our bounties

41-50: How about? They do not tell what it is

51-60: We are going to hack StarLink (they never say that, it is just the logo in the background when they are talking how easy it is to get in and out)

61-70: Dry Run, text scrolling on the screens

71-85: The Hack, split screens, zoom in and outs

86-88: Oh it was Solozzo (Binance) all along, not Starlink.

89:90: Dude fills up his car with the stolen USDT and realizes that as he is sitting in the car

dgrin91 20 minutes ago | parent

I wonder what the actual attack vectors here were. Was there actually a hack into binance systems, or was it just some insider or credential leak?

ActionHank 15 minutes ago | parent

Crazy thought, but what if they went via the Claude Code trojan?

gurkwart 19 minutes ago | parent

Something tells me that the timing of the Claude Code supply chain attack is not a coincidence ...

https://cyberplace.social/@GossiTheDog/117528831681803563

bagacrap 4 minutes ago | parent

Isn't the anthropic hack a day late?

bagacrap 2 minutes ago | parent

The funds were simply de-centralized. Seems by design?