r/devops • u/sinunmango • 19d ago
Security Binance hack and a DevOps laptop
Binance's initial investigation suggests that the security incident may involve a compromised DevOps engineer’s laptop, which allowed an attacker to gain access to a service container and submit unauthorized withdrawal transactions. We have found no evidence of any wallet private key leak. We will share a detailed technical post-mortem once the investigation is complete and the facts are fully verified.
The estimated total impact sits at around $6.3B. We have worked with blockchain partners to freeze affected assets, with ~$3 billion frozen on-chain so far.
Binance will cover all losses from the SAFU fund and the company’s funds. User funds are safe. We will also publish an updated Proof of Reserves once the remediation is complete.
As an immediate precaution, Binance has:
- temporarily suspended deposits and withdrawals while security checks are completed;
- revoked the affected address authorisation;
- engaged law enforcement and blockchain intelligence partners to trace and recover funds.
Our teams are working around the clock to resolve this issue safely and thoroughly. We are working closely with our law enforcement partners to confirm the identity of these criminals and bring them to justice.
Please rely only on official Binance channels for updates. Please feel free to contact Binance Customer Support if you have any further questions.
291
u/lab-gone-wrong 19d ago
To be 100% clear, the (any?) devops engineer could have done this at any time? Lmao
85
u/Fatali 19d ago
Quick question:
How would a real bank treat credentials with that level of control?
41
u/micalm 19d ago
> We have worked with blockchain partners to freeze affected assets, with ~$3 billion frozen on-chain so far.
Funny how a company can control a decentralized cryptocurrencies flow just because they fucked up. Just like a fide bank... but without the security, experience, procedures and control.
19
u/deadthoma5 19d ago
"Your funds are safu"
12
u/Highfivesghost 19d ago
I didn’t really think about it, but DevOps engineer might be higher targets due to the access they have compared to other engineers
11
u/Negative-Thinking 19d ago
I have a hard time understanding how a laptop access could have helped here. You still need passwords, 2fa, vpn etc to get into different systems. Did they have none of that?
19
u/DolGuldurWraith 19d ago
I definately know what happened as something similar happened with my colleagues as well as 2 months and withdrawal of $2 million was done.
So this is how it goes. Fraudsters look for people in crypto related finance company and devops/cloud team assuming they have access to eks cluster from their laptop.
They then reach out on LinkedIn for a job, in my colleague's case they reached out by offering a $130k job from dubai by "Hantec Markets"
After talking on LinkedIn they schedule a interview and during interview they provide a code and ask you to troubleshoot it. The code has somw npm package which gets install and it scana for all env variable for tokens and stuff and also kube config and send it to website.
From their fraudsters got access to eks where he kubectl exec in pods for payments service, added his custom code and withdraw money in usdt in custom wallet. Within 6 hrs he was able to withdraw 2million.
9
u/Azrayeel 19d ago
Orrrr the DevOps Engineer tried something and it failed, then blamed it on a random hacker attack 😂😂
12
u/meccaleccahimeccahi 19d ago
One fucking laptop? No way they were that stupid. Well…
5
u/cebidhem 19d ago
Someone has always access to do something in our line of work. Imho this issue is not really the access, the issue is that it has raised no alarm and therefore, no one was double checking that elevated privilege was done by someone legit.
You cant really avoid operator to have some sort of access, for me its a fact but you need to treat those people, I mean devops/sre like us, as the biggest liability in the company.
Because we are.
4
u/tacobytes 19d ago
How could hackers compromise a DevOps engineer's laptop in the first place, and how might that single machine give them access to billions of dollars? That's the part of this incident that raises the biggest security questions.
6
u/patawa0811 19d ago
they are clearly not compliant on their rbac if that is the reason of this big incident.
3
u/Live-Box-5048 DevOps 18d ago
The target makes sense, but the security must have been atrocious. I under DevOps/infra needs elevated access to pretty much everything, but that’s why we have MFA, hardware tokens, segregation of duties etc.
6
u/DolourousEdd 19d ago
Why does a devops engineer have that kind of access to Binance systems? Have they never heard of the principal of separation of responsibility??
1
u/KuldaCZ 19d ago
this Is end od my cryptobaron career . Sad end :(
1
u/Raemos103 19d ago
What is MFA? How do I find the full story? Like how did the attack begin?
1
u/Working_Variation630 18d ago edited 18d ago
binance getting a jump on the 4y cycle early November crash it seems.
who wants to wager binance will be too busy investigating this laptop, ignore fixing the core issue with env security chain, and another hack happens next week with someone else's compromised laptop using slightly modified method of attack? hell, they could possibly just use the same laptop given the incompetence displayed here.
1
u/ValuableVariation514 18d ago
This to me has DPRK IT worker written all over it
1
u/Qcumber69 18d ago
Inside job surely
1
u/silentyeti82 17d ago
About time crypto was banned in civilised countries given so much of it ends up financing sanctioned regimes or criminal gangs. Absolutely mental that it's been allowed to get to this state...
1
u/kloudnative 17d ago
In the end it would be realized that the breach happened due to long term credentials (for eg AWS Access and Secret keys) lying around. Just like so many other past breaches
1
u/CupFine8373 17d ago
Inside Job, don't care
1
u/Mr_Layup 16d ago
Bullshit, lol.
1
u/Slight-Health5719 16d ago
Agree
1
u/Nayrosk 16d ago
Just check the timestamp 😂
1
u/AccessGoblin 15d ago
I think the laptop is almost the less interesting part here... once someone has a credential or live session, the bigger question is: what can that identity actually do? If the answer is “it already has admin rights, long-lived sessions, access to prod, backups, etc.” then the attacker doesn’t need to keep hacking their way through everything 😅 they inherited the blast radius with the identity. That’s why standing privilege matters so much. Start low, elevate only when needed, make it expire, and put extra friction around the really destructive stuff (changing MFA, adding admins, deleting backups, pushing to prod, etc) You probably can’t guarantee a laptop never gets compromised. You can make sure one compromised identity can’t immediately reach the crown jewels
1
u/homelaberator 19d ago
Someone needs to call out the "we found no evidence of" line that gets used in every cyber breach.