>
So basically, the Google employee added arbitrary javascriptThis is a little disingenuous. She's a software engineer who works on this extension. "Injecting arbitrary JavaScript" is her job.
If she bypassed code review, introduced a vulnerability, abused a known weakness to violate policy (e.g. logged into an account with signing keys to deploy manually when it's usually automated), etc. then you'd have a case. If she did her job and followed all policies about review and the only question is the content of the notification, then the way she sent it is an unfair criticism. It reeks of CFAA-style stretching of the truth about authorized access, and we as hackers shouldn't stand for it.
I wrote a command-line tool at work to automatically add a bunch of party parrots to a Slack message. This tool runs with your personal credentials, and web-scrapes your Slack access token in order to run. As a normal UNIX tool it also has access to your homedir etc. The credentials it uses can also read your private Slack DMs, access data that you can get to but I am legally forbidden from seeing, etc. - but it does none of those things. I installed it to a bin directory in everyone's path, without code review, because we have a system that explicitly allows this and it is often useful. Our security team raised a general ticket to the effect of, hm, maybe code review should be required before you stick code in everyone's PATH. Nobody is thinking of firing me for "injecting arbitrary Python" or "stealing credentials" or anything because nothing I did was against either policy or convention, even though you can make it sound horrid if you choose.