I haven’t heard of #Giggle before but apparently they not only had a pretty bad vulnerability allowing anybody to query information of all accounts, they also made some rather questionable privacy choices. https://research.digitalinterruption.com/2020/09/10/giggle-laughable-security/
According to the researchers, they were first ignored when they attempted to report the issue. Eventually, they received a response but not the kind they hoped for. Not sure why they had to state their disagreement with @firstname.lastname@example.org’s views, but it clearly rubbed her the wrong way.
From that point on, things went only downhill. @salltweets vehemently denied the existence of any security issues, claiming that the whole thing is a harassment campaign – despite not having received any details. She sent them a DM but apparently blocked the account later.
She says that they should have emailed technical department directly – yet from a brief look I cannot find the corresponding email address anywhere. From experience, emailing technical support about vulnerabilities is a bad idea. So Twitter is a valid way to approach a company.
And she claims that @DI_Security@twitter.com researchers publicly called her a transphobe. Not sure what this is about, I could only find a tweet by @email@example.com who appears to have no relation to the researchers. Judging by the way @firstname.lastname@example.org responded she thinks otherwise.
So today she proceeded by once again attacking the researchers and criticizing journalists who were asking her about the security vulnerability, restating that it didn't exist.
Somehow, the email communication still happened, the right person received the report and confirmed it. So a bit later today @email@example.com started sharing the image below – without retracting any of her claims, somehow assuming that this reinforces her points.
The good news is: the vulnerability has been fixed. The researchers had to publish their findings early given the repeated attempts to undermine their credibility. The questions about privacy issues remain of course.
The bad news: @firstname.lastname@example.org threatens to sue the researchers unless they let her approve the publication first. They kindly decline, as they should. And she shares that communication publicly as well, somehow assuming that it puts her in a better light?
A Mastodon instance for info/cyber security-minded people.