News for hackers. Stuff that matters.
Re:Mudge Twitter whistleblower testimony [video] by ryzvonusef on Tuesday September 13, 2022 @10:46AM (#32824957)
https://twitter.com/donie/status/1569695781631688704

> "It's not far fetched to say an employee inside the company could take over the accounts of all the Senators in this room," @dotMudge with a warning here on Captiol Hill. #Twitter

perhaps a valid reason?

Re:Mudge Twitter whistleblower testimony [video] by bradleybuda on Tuesday September 13, 2022 @11:23AM (#32825502)
It's not far fetched to say a Senator's pilot could drop their airplane into the Delaware.

It's not far fetched to say a the line cook at a Senator's restaurant could poison their food.

It's not far fetched to say that a Senator's financial advisor could run off with their money.

It's not far fetched to say the teachers who instruct a Senator's kids could fill their heads with lies.

Humans have all sorts of ways to wreak destruction on one another but it mostly doesn't happen, and when it does, we have many, many systems in place to detect and punish. And we tend to scale the weight of these systems to the size of the perceived threat - that's why doctors and pilots are more burdened than bankers who are more burdened than cooks.

How likely is someone to actually take over these accounts (what's to gain)? How much damage would it do (not too much, people get hacked on Twitter all the time and that's baked in to the credulity of each tweet)? How likely is that employee to get caught (high), and how much punishment would they face (huge fines, possible jail time, unemployable in many industries for the rest of their lives).

Technical safeguards are not our only safeguards, especially for insider threats, which long predate the Internet. External hackers do dramatically change the calculus here (unlikely to get caught or punished) but that's not what's being alleged.

Re:Mudge Twitter whistleblower testimony [video] by pclmulqdq on Tuesday September 13, 2022 @11:46AM (#32825841)
Technical safeguards against insider threats do not actually protect you from insider threats - the fact that your behavior is logged and you will get fired and sued into oblivion works very well.

Technical safeguards against insider threats protect your insiders. They give your insiders cover in situations where they might be coerced to do things.

When I was at G, I likely could have read some data from cloud customers with some social engineering and the permissions I had. It would have taken hours to get the first byte, and I would have been fired within 10 minutes if I did without a good reason. The fact that it would have taken hours and some social engineering would let me plausibly tell the police (or the Chinese government or the mob or anyone else), "no, I don't have access to that data." Twitter's engineers didn't have that cover.

Re:Mudge Twitter whistleblower testimony [video] by MattPalmer1086 on Tuesday September 13, 2022 @02:26PM (#32828329)
I like your take on it providing cover for insiders against coercion. I hadn't considered that aspect before.

I'd slightly disagree that technical safeguards don't provide any protection against insider attacks. But yes, the deterrent effect of having a high chance of being caught is very effective.

Re:Mudge Twitter whistleblower testimony [video] by sangnoir on Tuesday September 13, 2022 @08:51PM (#32831984)
Weren't those controls added after some Googler stalked teenagers[1] via their chats for months? That event generated bad publicity in the press, and some years later, the same thing happened at Uber, with the euphemism "LoveOPS" being used, IIRC.

High-growth companies prefer to prioritize features and kick the access control can down the lane until they absolutely have to. Without looking at revenue and employee numbers, I suspect 2010 Google and 2016-ish Uber are comparable to current Twitter, IMO.

Edit: the Googler story is far worse that I remembered: he had unfettered access to underaged victims' mailboxes, chat logs, contacts and Voice accounts and used that information to taunt one victim, and unblocked himself from another victim who had blocked him on Gchat - Google only became aware of it when it was reported externally.

1. https://www.businessinsider.com/google-engineer-stalked-teen...

Re:Mudge Twitter whistleblower testimony [video] by pclmulqdq on Tuesday September 13, 2022 @09:16PM (#32832156)
That incident inspired the alerts and the permissions checks. There were a few other incidents (not heinously bad if they were public, but potentially bad for G) that made them go all the way.
Re:Mudge Twitter whistleblower testimony [video] by bink on Tuesday September 13, 2022 @01:03PM (#32827062)
Not to defend Twitter because their lack of oversight and security controls around who can access what sounds completely inadequate and borderline criminal... but comparing any company to Google is unfair. Very, very few companies have the resources and experience that Google has dealing with these types of threats.
Re:Mudge Twitter whistleblower testimony [video] by michaelt on Tuesday September 13, 2022 @11:49AM (#32825885)
> It is not far fetched to say a Senator's pilot could drop their airplane into the Delaware.

Aviation has the state imposing licensing requirements, the state certifying which vehicles can take passengers, the state imposing technical requirements like transponders, the state investigating accidents, the state telling pilots when they can take off and land, the state searching passengers' luggage and sending them shuffling through scanners without their shoes, the state establishing no-fly lists, and the state wading into the industry and choosing winners and losers whenever it's geopolically convenient.

If you tell the senate you'd like the tech industry to be regulated no more heavily than the aviation industry we'd be in for a lot more regulation.

Re:Mudge Twitter whistleblower testimony [video] by bradleybuda on Tuesday September 13, 2022 @12:05PM (#32826129)
> [...] we tend to scale the weight of these systems to the size of the perceived threat - that's why doctors and pilots are more burdened than bankers who are more burdened than cooks
Re:Mudge Twitter whistleblower testimony [video] by madeofpalk on Tuesday September 13, 2022 @12:06PM (#32826143)
> How likely is someone to actually take over these accounts? How much damage would it do?

We kind of have answers to these questions already:

- A rogue employee/contractor deactivated Trump's account back in 2017 https://www.theguardian.com/technology/2017/nov/03/experts-w...

- "130 high-profile Twitter accounts [including Apple, Barack Obama, Joe Biden, and Bill Gates] were compromised by outside parties to promote a bitcoin scam" using internal Twitter admin tools. https://en.wikipedia.org/wiki/2020_Twitter_account_hijacking

The impact of both of these was basically zero.

Re:Mudge Twitter whistleblower testimony [video] by saltminer on Tuesday September 13, 2022 @12:59PM (#32826995)
There's also the fact that entire forums exist around selling accounts (or access to accounts). One such site, swapd.co, has a pinned post for Twitter "username claims" and "account recovery", among other things. This site has sold admin panel access that has been responsible for a lot of crypto scams [0] in the past.

Nobody's account is safe. Doesn't matter what 2FA methods you use, whether you're verified or not, how many followers you have, all it takes is a couple grand for someone else to take it over.

> The impact of both of these was basically zero.

Per the Wikipedia article you linked, the attackers got $110k in Bitcoin, which is not "basically zero" (even if the price of BTC has fallen since then).

[0]: https://www.web3isgoinggreat.com/?id=researcher-zachxbt-alle...

Re:Mudge Twitter whistleblower testimony [video] by ohgodplsno on Tuesday September 13, 2022 @02:57PM (#32828728)
If taking over more than 100, extremely high profile accounts with millions upon millions of followers only nets you 100k and puts massive visibility on you, it's basically zero.
Re:Mudge Twitter whistleblower testimony [video] by aaaaaaaaata on Tuesday September 13, 2022 @11:39PM (#32833096)
And yet it's still happening.
Re:Mudge Twitter whistleblower testimony [video] by tschwimmer on Tuesday September 13, 2022 @12:50PM (#32826844)
Is it true that the impact of these incidents was zero? How much money did the bitcoin scam guys get?
Re:Mudge Twitter whistleblower testimony [video] by codyb on Tuesday September 13, 2022 @10:49AM (#32824979)
They probably have a way to take over accounts to check bug reports.

We've had that at places I've worked. Where you'd be able to impersonate a user in order to see what was going on with their specific set of user data to corroborate their report and find a fix.

The question is... are the permissions locked down, is access audited and immutable, etc I think.

Re:Mudge Twitter whistleblower testimony [video] by bombcar on Tuesday September 13, 2022 @10:50AM (#32825004)
Yep, there's lots of software with "su for X" capabilities; it's much better than the normal method which is "ok tell me your password and I'll login as you and see what's up".
Re:Mudge Twitter whistleblower testimony [video] by AndrewStephens on Tuesday September 13, 2022 @10:53AM (#32825053)
Well Duh! Of course a twitter employee could take over any account. Hopefully they have some internal safeguards in place but there are probably hundreds of people there that could take over an account if they wanted to, just as the owners of news.ycombinator.com could take over any account here.

You don't really own a Twitter (or Facebook, or ycombinator) account. Those services have an account on you. You update their account on you when you use their service to post (and they keep other information useful to their business on your account that you have no access to).

This is just the way social media works.

Re:Mudge Twitter whistleblower testimony [video] by michaelt on Tuesday September 13, 2022 @11:08AM (#32825283)
> Well Duh! Of course a twitter employee could take over any account.

Most companies the size of Twitter would have a lot more controls than that on random employees' write access to production.

If I want to assume a user's identity in my employer's production system I have to fill out a form justifying it, get my manager's approval for each account accessed, and my activity is subject to logging.

Re:Mudge Twitter whistleblower testimony [video] by madeofpalk on Tuesday September 13, 2022 @12:07PM (#32826165)
Re:Mudge Twitter whistleblower testimony [video] by themaninthedark on Tuesday September 13, 2022 @12:21PM (#32826385)
Remember when an employee took down Trumps account? https://news.yahoo.com/rogue-twitter-employee-took-down-1419...

First it was "inadvertently deactivated due to human error by a Twitter employee." Then "Through our investigation we have learned that this was done by a Twitter customer support employee who did this on the employee’s last day."

It was kinda funny but you would expect that they would learn and improve from it.

Edit: Thank you siblings for showing that it has continued to happen. Obviously not lesson not learnt.

Re:Mudge Twitter whistleblower testimony [video] by encryptluks2 on Tuesday September 13, 2022 @11:52AM (#32825924)
So it can still be done, isn't that the original complaint?
Re:Mudge Twitter whistleblower testimony [video] by armchairhacker on Tuesday September 13, 2022 @12:18PM (#32826349)
The point is that politicians shouldn’t be posting their important messages on Twitter, but an official government channel. This was discussed in 2016
Re:Mudge Twitter whistleblower testimony [video] by Anon1096 on Tuesday September 13, 2022 @11:05AM (#32825238)
Was there an expectation of the opposite being true? You don't own a social media account. See all the people banned, shadowbanned, or who have had their @ handle or blue checkmarks taken from them. I thought it was accepted that the service provider can do whatever they want with a given account.
Re:Mudge Twitter whistleblower testimony [video] by zamalek on Tuesday September 13, 2022 @11:05AM (#32825250)
> perhaps a valid reason?

That's why I specifically said "from a naive standpoint." I'm not arguing against valid reasons, I'm pointing out how absurd the situation is.

From my comment:

> I understand that there are consequences of Mudge's information