[ 3 / biz / cgl / ck / diy / fa / ic / jp / lit / sci / vr / vt ] [ index / top / reports ] [ become a patron ] [ status ]
2023-11: Warosu is now out of extended maintenance.

/biz/ - Business & Finance

View post   
File: 94 KB, 615x717, Screenshot_20180307_173536.png [View same] [iqdb] [saucenao] [google]
8180936 No.8180936 [Reply] [Original]

It appears Binance was hacked:
https://twitter.com/674ac/status/971409543841361920/photo/1

>> No.8180963
File: 79 KB, 1934x1141, Screenshot_20180307_173736.png [View same] [iqdb] [saucenao] [google]
8180963

Market agrees

>> No.8181018

>>8180936
https://coinmarketcap.com/currencies/viacoin/#charts


kek

>> No.8181082

>>8180936
1. We already know faggot

2. Only happened to the faggots who gave api keys to third parties (aka retards). They deserved it.

My binance funds are comfy.

>> No.8181113

>>8181082
>2. Only happened to the faggots who gave api keys to third parties (aka retards). They deserved it.
Get rekt botters.
ahahaha

>> No.8181174

show me your pinkest wojack anon

>> No.8181189
File: 235 KB, 426x585, 831.png [View same] [iqdb] [saucenao] [google]
8181189

time 2 buy

>> No.8181278
File: 36 KB, 920x479, no bots.png [View same] [iqdb] [saucenao] [google]
8181278

>>8181082
I also work at binance so I can confirm it wasn't binance fault

>> No.8181353
File: 51 KB, 500x500, 1519287841843.jpg [View same] [iqdb] [saucenao] [google]
8181353

>BITTCOIN IS THE FUTURE
>ITS SO SECURE NO ONE CAN TOUCH IT
And yet we have bittcoin hacks that steal billions of dollars every weak.
amazing technology

>> No.8181409

>>8181353
>Have a technology that is decentralized
>People store them on a centralized exchange
Why

>> No.8181493
File: 1.19 MB, 768x432, matureblondewomansharpeningaknife.webm [View same] [iqdb] [saucenao] [google]
8181493

>>8181409
this 2bh f4m
nobody can take any crypto seriously until the majority of people start using decentralised exchanges although I doubt this will ever happen

>> No.8181548

>>8181353
>YOU ARE YOUR OWN BANK
>puts money on an exchange
>doesn't secure own wallet

amazing hopes of future progress dashed in an instant

>> No.8181565

>>8181353
exchanges arent even on-chain
they can just rollback their database and all is fine

there's literally no reason for them not to immediately do this, they'd lose all credibility unless they can prove how the hack happened and it only happened due to human error of all those users

>> No.8181725

>>8181565
Those who went into tether would lose money.

>> No.8181866

>>8180936
mfw tethered up at 11636 because daily stochastic was oversold and expected correction

>> No.8181924

>>8181082
I gave my API keys to an app but only with read access, as of yet nothing's been compromised. Am I safe? Or I revoke access to API key?

>> No.8181941

>>8181725
so would people who sold via on ath
but desu this is a pretty easy decision for binance

>> No.8182160

>>8181924
imo binance used a simple algorithm to bind api keys to the user account, so it doesnt matter if you gave access to them, hackers probably found a way to regenerate them based on something available
they could also have brute forced them over months and just accumulated a long list of those that work, this can go undetected because they dont have to actually do trades to test if the tokens work

its another nice side effect of having massive mining farms if that you can brute force such things relatively easy

>> No.8182744

I'm not concerned, my $76.23 is right where I left it

>> No.8182918
File: 19 KB, 368x350, Yawning.jpg [View same] [iqdb] [saucenao] [google]
8182918

>ah, the weekly Binance hack

>> No.8182943

>>8181924
Read access means you're fine. Anything else is FUD.

>> No.8182966

>Americans wake up
>Instead of lurking on the latest news, they go to twitter and read literal who's post and post on /biz/ like they're knowledgable about something instead of being ignorant as always

>> No.8182978

>>8181082
this. also happened on other exchanges

>> No.8183005

>>8182160

This is complete nonsense technical mumbo jumbo made to scare people.

There is no "simple algorithm" to bind api keys to a user account. The api key is a database field with an id that points to an account based off the account's id. There's no fucking algorithm, it's simple database shit.

Explain to me how a hacker "regenerates" api keys through brute force. Explain what that means.

Jesus fuck who is paying you ?

>> No.8183018

>>8181493
Source

>> No.8183030
File: 23 KB, 399x370, 1519325193398.jpg [View same] [iqdb] [saucenao] [google]
8183030

>>8182966
>Americans wake up
>They lost their money due to "hacks"
Fucking mutt brainlets lmao

>> No.8183057

>>8180936
>keeping your coins on an exchange
Literally deserve everything that happens to you if you do this.

>> No.8183072

>>8183005
STFU retarded burger what he says makes complete sense, weak salting. Go back to facebook retard.

>> No.8183121

Why is my twitter on /biz/? This was old news before I even tweeted it. Delete this.

>> No.8183156

>>8183057
nothing to do with the exchange platform, newfag

>> No.8183169

>>8180936
So the hacker already withdrew all the btc?

>> No.8183198

>>8181493
Sauce?? For the love of god, sauce

>> No.8183268

>>8180936
B-BUT ASIANS ARE THE MODEL MINORITY. THEY DON'T COMMIT CRIMES. THEY DIDN'T HACK THE BOT ALGORITHMS ON PURPOSE TO STEAL BTC FROM STUPID WESTERNER KEKS. ONCE CHINA RULES THE WORLD, WE WILL ALL BE IN GOOD HANDS.

>> No.8183454
File: 19 KB, 237x229, 1388311321992.jpg [View same] [iqdb] [saucenao] [google]
8183454

It's not an exchange hack, you fucking idiots.

There are only 2 scenarios that could have happened, neither of which where Binance was at fault:

Scenario 1:
>Phishing site

Scenario 2:
>Malware, probably injected through ICO websites.

Whichever happened, they probably played it off something like this:
>Users entered their login + 2FA
>The attackers logged in with these settings on the users Binance account, activated trading APIs, stored the keys and lied in wait
>They emptied whichever accounts didn't have 2FA, and did a co-ordinated pump and dump with all the accounts using 2FA, because of the impossibility of withdrawing from the accounts

>> No.8183649

>>8183268
Everyone knows the Chinese are autistic turbo-Jews. They just don't stab you randomly on the street like niggers do. Only the Japs are honorabor.

>> No.8183771

>>8183005
i didnt say thats exactly what happened, but obviously api keys are generated from something, like a generator algorithm
its unlikely that they used a completely random algorithm and just kept them in a database entry because that makes it impossible to verify if a token belongs to a user without having access to the database, you'll also want to do this offline or within a program that can't check the database hundreds of times per second. thus there probably IS a "simple" correlation from useraccount to api keys, in the worst case it could be the hash of the sending address (a complete guess obviously, would be criminally incompetent since they're all publicly available)

this is all hypothetical because I do give people the benefit of the doubt that they havent been sharing their api keys en masse as it seems to be the case. brute forcing is always a possibility, never argue with it, especially if its just a short string of defined characters