Google purges bad extensions from Chrome
1–10 of 93 posts
Re: Google purges bad extensions from Chrome
#2 1. The user logs in to his/her online banking website.
2. The malware gets triggered and phones home with user's credentials.
3. The bad guy logs in using user's credentials in own computer.
4. The bad guy initiates bank transfer from user's account to his account.
4. The bad guy is presented with "enter auth code" to confirm the transaction.
5. The malware pops up "Verify your auth code" into user's computer.
6. Thinking "it must be new method from my bank", user types his/her auth code.
7. The auth code gets sent to the bad guy, allowing him to complete transaction.
8. Profit.
Even tech savvy people can be a victim if he's being careless.Re: Google purges bad extensions from Chrome
#3Re: Google purges bad extensions from Chrome
#4Which is usually accompanied by the developer apologising and explaining they have to declare this in order to provide the extension's core functionality. Users then learn to ignore these warnings, malicious extensions ensue.
I'm glad Google is taking malicious extensions seriously, but purging is a difficult semi-manual effort when extensions can update any time. A lot more effective would be to bake security into the whole model. Extensions shouldn't need to see your entire browsing history on all sites just to enhance some links or do syntax highlighting.
It should also be possible to request permissions on demand, and for certain URLs, instead of blanket-consenting before the extension is even installed. I know these things are a trade-off with simplicity, but should at least be there for orgs and individuals who want to take advantage of them.
Re: Google purges bad extensions from Chrome
#5Does anyone know where one could find a list of offending plugins? I tried, but came up empty handed.
Re: Google purges bad extensions from Chrome
#6As an aside, I'm surprised at how willing most users seem to be to install any software, be it browser extensions or random apps on their phones/tablets/PCs. Especially in the case of deliberately malicious extensions mentioned in the article, I wonder if they were installed without the user ever considering "What is this for? Do I really need it?"
Re: Google purges bad extensions from Chrome
#7"This extension will have access to your browsing history and private data on all websites". Which is usually accompanied by the developer apologising and explaining they have to declare this in order to provide the extension's core functionality. Users then learn to ignore these warnings, malicious extensions ensue. I'm glad Google is taking malicious extensions seriously, but purging is a difficult semi-manual effo…
Re: Google purges bad extensions from Chrome
#8Aren't extensions written in JavaScript? That alone sounds like it'd make it pretty easy to examine and remove any "unwanted functionality" from one, or to show that it's doing something it shouldn't be. It only takes one knowledgeable user to find out and spread the news... As an aside, I'm surprised at how willing most users seem to be to install any software, be it browser extensions or random apps on their phones…
Re: Google purges bad extensions from Chrome
#9The Quick Note Chrome extension from Diigo (now removed) submits every URL visited to a third-party server and those URLs are then crawled the next day.
We just switched our 25 member customer service team to Chromeboxes and were very concerned to find soon after that an EC2-based crawler was querying private URLs of our platform.
Because the Chrome Web Store had not banned bad actors like Diigo, we now blacklisted all Chrome extensions except for a very small number that I personally approve. Rather than feeling that ChromeOS was improving our security, we had our chief software architect spend most of the weekend figuring out who was targeting our platform. (All queries received 404 errors, but we remained concerned whether the rogue extension could read the submitted form credentials or the cookie store to get access.)
Rogue extensions are wasting a huge amount of time and destroying trust in the Chrome platform. Here's some more detail on similar stories about Diigo:
https://chrisa.wordpress.com/2014/08/25/chrome-extensions-go... https://mig5.net/content/awesome-screenshot-and-niki-bot
I am thrilled to see Google finally acting to restore trust in their platform.
Update: Google removed Diigo Quick Note, but still has Awesome Screenshot " rel="nofollow">https://chrome.google.com/webstore/search/diigo?hl=en-US> which captures the identical data and sells it to third party crawlers.
Re: Google purges bad extensions from Chrome
#10Aren't extensions written in JavaScript? That alone sounds like it'd make it pretty easy to examine and remove any "unwanted functionality" from one, or to show that it's doing something it shouldn't be. It only takes one knowledgeable user to find out and spread the news... As an aside, I'm surprised at how willing most users seem to be to install any software, be it browser extensions or random apps on their phones…