Quote from: cAPSLOCK on Today at 05:43:05 PM

Quote from: Biodom on Today at 04:09:57 PM

These links provides the most accurate info, I think:

https://finance.yahoo.com/news/coinbase-stock-slips-crypto-exchange-123040251.html

Quote

Coinbase said no passwords or customer funds were ever accessed. However, it said names, addresses, phone numbers, email addresses, last four digits of Social Security numbers, masked bank account numbers, and Coinbase account data like "balance snapshots and transaction history" may have been compromised.

They also said that access was from outside of US, but it is not clear where the customers were.

https://www.investing.com/news/stock-market-news/coinbase-discloses-security-breach-expects-impact-of-up-to-400m-4047654

The breach, which Coinbase described as an “extortion attempt,” is said to have started when criminals bribed overseas support contractors to extract internal data affecting less than 1% of monthly transacting users.

The attackers reportedly obtained names, addresses, and phone numbers, as well as masked Social Security [it means just the last four digits] and bank account information, government ID images, and account data.

Coinbase emphasized that the attackers did not gain access to passwords, two-factor authentication codes, private keys, or customer funds.

I think this has to be Coinbase PR, I bolded the really, really important thing that they seem to be trying to slip under the radar.

Say someone has even a reasonably small number of whole Bitcoin on their Coinbase account. That's worth a lot of money nowadays and the attackers know who has Large holdings or even have transferred large amounts off to their own storage and they have their names, addresses, phone numbers, pictures, drivers license, etc. etc. This is very dangerous for people who would be someone worth flying out to with a $5 wrench.

Seriously, if any of you in here fit that description, I would try to find out as quickly as possible if your account was one of the ones compromised. And if so, I don't know what you should do, but you should take some kind of precaution I would think, at least by a gun.

First of all, it's still don't trust, verify.
But nobody can verify what coinbase is telling us.
So they don't deserve to be trusted, or at least trusted in regards that can be verified.
As far as i correctly understood him (honestly, i don't happen to memorize his name, maybe because i care so little about this guy) in the video message, the customers in scope of the breach are being informed, but i was distracted by people around me while watching it.

But the thing with the gun... This isn't enough. Awareness and gun training are really important. There are also legal issues to take care of if you want to hold or use a gun in different countries. But learning to be aware of your surroundings is key to prepare for possible attacks. The bad boys don't drive up at your house, break open a window and start working you with the wrench, they likely observe and collect information in advance. Unfortunately, as i use powerful optics for one of my hobbies, i know how easy it is to observe from a big distance, which makes the observers much less visible. If one has the money (and a house), a panic room would be a good option, because it can be used by other familiy and household members in an emergency. Thinking of the cut off fingers in France to extort private keys from relatives...
I could go on, this topic can get quite complex, at least we can agree that it sucks more than almost anything else to get your personal data leaked when you're holding Bitcoin.

Quote from: goldkingcoiner on Today at 05:58:21 PM

~~Not your keys not your coins~~
Not your server, not your data.

Quote from: goldkingcoiner on March 22, 2024, 12:06:26 PM

Stay away from centralized exchanges. They will find ways to extort your KYC as well as your money from you. And they will probably sell your data (passport and so on...) and they will claim it was due to a "hack" to avoid responsiblity.

Incoming identity thefts in 3...2...

That's exactly one of the facades of the trust/verify problem.