Email or username:

Password:

Forgot your password?
Top-level
Dan

@dplattsf @pjohanneson @thomasfuchs credential stuffing is a standard attack. not protecting against it, then lying about how many people were affected, then back-door changing their TOS to disallow compensation, those are reasons they should be pilloried and compensate people affected.

15 comments
Peter

@dko @dplattsf @pjohanneson @thomasfuchs

yeah the "crime" here is the legal coverup. this is some serious dark pattern stuff here.

Dan

@pjm @dplattsf @pjohanneson @thomasfuchs Ya know, one specific person's prior couple of posts have rustled my jimmies.

There are a couple of things to unpack and de-shit here.

1) "you leave your DNA everywhere you go":

Sure, yes. HOWEVER! It's not sequenced and ready to be used by whomever for absolutely any purpose. I have basically zero concern about this being an issue with offshore ransomware syndicates.

I have A LOT OF CONCERN about this being harvested by any of the major databrokers and used to deny people healthcare because of their genome, which those folks never consented to share with the people who make decisions about whether they live or die

2) 23andme said fewer than 1% of users were affected. it turns out, 50% are affected because of sharing settings.

why the fuck is my data subject to exfiltration because of another user? I can't imagine that it was exfiltrated by forging browser or API sessions and requesting the data. it smells a lot like shitty database structure.

I guess unless they release a very detailed IR report we'll never know.

3) blaming users for "doing the bad thing" is an abdication of responsibility as an admin.

there are simple ways to guard against these sorts of attacks. i don't know 23andme's stack or how difficult it would be to implement, but at a very basic level, here's a good start:

-

robust password policy - minimum 8 char password, disallow at least the top 100 from HIBP and/or rockyou, if not the top 1000


-

require 2fa


-

disallow anything that looks like probing activity. any accounts that are logged in within 60 mins from the same IP, any IPs that show logins to multiple accounts with incorrect passwords, etc, etc

@pjm @dplattsf @pjohanneson @thomasfuchs Ya know, one specific person's prior couple of posts have rustled my jimmies.

There are a couple of things to unpack and de-shit here.

1) "you leave your DNA everywhere you go":

Sure, yes. HOWEVER! It's not sequenced and ready to be used by whomever for absolutely any purpose. I have basically zero concern about this being an issue with offshore ransomware syndicates.

pa27

@dko @pjm @dplattsf @pjohanneson @thomasfuchs

The healthcare point is interesting. I would like to think that any healthcare organisation using unverified, stolen data to make decisions about a client would themselves be subject to massive class actions...

robotmascot

@pa27 @dko @pjm @dplattsf @pjohanneson @thomasfuchs

Seems VERY easy to do parallel construction with this stuff- once you have the conclusion in hand from the illegally-gathered evidence, it's not hard to create an in-the-clear paper trail with legal evidence leading to that same conclusion and pretend the 'dark' evidence never happened.

Darren

@pjohanneson @dko @thomasfuchs have you been to haveibeenpwned lately? The only thing that distinguishes this from a typical day on the internet is that it has the word dna in it and they didn’t even get hacked. Going to save up my outrage ..

Dan

@dplattsf @pjohanneson @thomasfuchs "People get breached" is not a good argument against getting breached.

And speaking of Troy's site, why didn't 23andme disallow the top 1000 passwords from HIBP or at least rockyou?

why didn't they disallow tons of requests probing passwords?

why didn't they require 2fa?

any of these would likely have prevented this. all of them together would almost certainly have.

who are you helping here? a company that just made millions of people's genomes public with their indefensible policies?

@dplattsf @pjohanneson @thomasfuchs "People get breached" is not a good argument against getting breached.

And speaking of Troy's site, why didn't 23andme disallow the top 1000 passwords from HIBP or at least rockyou?

why didn't they disallow tons of requests probing passwords?

why didn't they require 2fa?

Darren

@dko @thomasfuchs @pjohanneson same reason your bank is still using sms for 2fa. people get upset if you force them to do it the right way. and they get outraged if you don’t. This would be the perfect setup for #GWAS on #password and #2fa hygiene

Dan

@dplattsf @thomasfuchs @pjohanneson again, who are you arguing for here? companies with shitty policies? companies that leak DNA data?

why are you just naming bad practices as if they justify more bad practices?

"bad things have happened and unconcerned people are responsible" is not a defense for bad engineering that endangers your users.

Darren

@dko @thomasfuchs @pjohanneson just trying to understand the outrage and indignation here - again they’re well within the norm for orgs and they also didn’t get any of their systems breached so saying they were hacked is misinformation. They have normal users doing normal bad things. but it’s dna so .. .. .. must be so much worse ? People need recalibration.

Dan replied to Darren

@dplattsf @thomasfuchs @pjohanneson "well within the norm" is not a security standard. that's not what users signed up for and if it were plainly stated no one would ever reveal identifying data to these people, let alone their genome.

How are you not getting why this is a significant breach?

Data brokers have no "do not buy list". They will get any info from any source that's available.

"didn't get their systems breached" is not a statement i would make if 14,000 user accounts were compromised, which later led to disclosing the data of 50% of your users.

you know the first thing the attackers did was release a million lines of user data, right? for free, right away, and all of those users were jewish

can you see how this data could be misused now?

nbcnews.com/news/us-news/23and

@dplattsf @thomasfuchs @pjohanneson "well within the norm" is not a security standard. that's not what users signed up for and if it were plainly stated no one would ever reveal identifying data to these people, let alone their genome.

How are you not getting why this is a significant breach?

Data brokers have no "do not buy list". They will get any info from any source that's available.

DELETED replied to Dan

@dko @dplattsf @thomasfuchs @pjohanneson

I work in this field.

It was a credential stuffing attack. Google that. There wasn't much they could have done about it.

However, Everything they've done after the fact has revealed them to be the shitty corporation that most corporations eventually reveal themselves to be.

It's a breach, but not like a breach where there were default creds exposed on the internet (equifax) or some idiot (LastPass).

Cybarbie replied to DELETED

@BigMcLargeHuge @dko @dplattsf @thomasfuchs @pjohanneson

You work in what field? There absolutely are many very effective ways to make sure your idiot users do not choose bad passwords. You could for example make them accept an autogenerated one, enforce some sort of second check - perhaps you are familiar with when you get a pin sent to you on your phone? We can already tell their users are people who do not care about their own or their families privacy and so probably warrant extra checks.

paradx

@dplattsf @dko @thomasfuchs @pjohanneson the bank is using 2fa though, and given the sensitivity of the data, I would think even doing shitty 2fa would have helped.

chriszanf

@dko @dplattsf @pjohanneson @thomasfuchs
If they cared about security, they would have scanned their userbase cross referencing the emails on HIBP & forced an email change on them.

If they cared about their users data, they would have implemented MFA to minimise 'weakest link' vector.

Francis 🏴‍☠️ Gulotta

@dko @dplattsf @pjohanneson @thomasfuchs even the basic email challenge 2fa they use now protects users plenty more than they were before

Go Up