Chrome Extension Developers Under a Barrage of Phishing Attacks (bleepingcomputer.com)
An anonymous reader quotes Bleeping Computer:
Google's security team has sent out warnings via email to Chrome extension developers after many of them have been the targets of phishing attacks, some of which have been successful and resulted in crooks taking over extensions. These phishing attacks have come into the limelight this past week when phishers managed to compromise the developer accounts for two very popular Chrome extensions -- Copyfish and Web Developer. The phishers used access to these developer accounts to insert adware code inside the extensions and push out a malicious update that overlaid ads on top of web pages users were navigating.
According to new information obtained by Bleeping Computer, these attacks started over two months ago and had been silently going on without anyone noticing. All phishing emails contained the same lure -- someone posing as Google was informing extension developers that their add-on broke Chrome Web Store rules and needed to be updated. The extension developer was lured onto a site to view what was the problem and possibly update the extension. Before seeing the alert, the site asked extension developers to log in with their Google developer account, a natural step when accessing a secure backend.
According to new information obtained by Bleeping Computer, these attacks started over two months ago and had been silently going on without anyone noticing. All phishing emails contained the same lure -- someone posing as Google was informing extension developers that their add-on broke Chrome Web Store rules and needed to be updated. The extension developer was lured onto a site to view what was the problem and possibly update the extension. Before seeing the alert, the site asked extension developers to log in with their Google developer account, a natural step when accessing a secure backend.
i'll let you stick it in my bum for a dollar.
Then start squawking OMFG RUSSIANS!!!
french toast and g'day, m'ladies
Are they saying that even developers just click without looking?
dear god, you're making my butthole wet.
So lately Firefox has been adding support for WebExtensions extensions, which is basically Chrome's extension model but for Firefox. As that page says, "Much of the specifics of the new API are similar to the Blink extension API". It's yet another case of Firefox's developers essentially cloning what Chrome did, even if Firefox's users don't want that at all.
Now we're hearing that Firefox 57 will only support support WebExtensions extensions. That will likely mean that a lot of extensions will break for a lot of Firefox users come this November.
It's bad enough that when these existing extensions break, many Firefox users will probably just move to Chrome instead. After all, if they need to start using Chrome-compatible browser extensions, why not just use Chrome directly? It's faster than Firefox. It uses less memory than Firefox. Its UI is a lot like Firefox's, due to Firefox's devs changing Firefox's UI to be similar to Chrome's. Firefox's privacy isn't even really better, since its privacy policy states that Firefox's geolocation support can use a Google service, thus sending some information to Google even if the user is using Firefox. So as of Firefox 57, Firefox users might as well just use Chrome (or one of the other browsers using the Blink engine) directly, instead of using Firefox.
If Chrome's extensions can be compromised in this way, then are Firefox's new WebExtensions extensions also susceptible? Is Mozilla doing anything to protect Firefox users from such a threat?
(Though after W10 it's not like we need any extra reasons)
cite
The fans are gonna do what they are gonna do.
Why would someone need to move to using Chrome *instead of* Firefox?
I'm sure I'm not the only one who uses multiple browsers, each with different settings, for varied purposes, and will continue to do so.
And maybe someone clueless enough to fall for this kind of tricks (bogus phishing links) wouldn't be the best person to trust with your web security (the web extensions they write are probably full of exploitable bugs and flaws).
"Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
i'm such a goddamn faggot
Firefox's CURRENT extensions are susceptible. The threat is that someone takes over a developer account and then uploads a malicious version of the current extension to the extension update service. There's no reason to believe that such a thing wouldn't be possible with Firefox. Just like Chrome, you need an account with Firefox for them to host your extension in their addon store ... repository ... thing.
The only thing that makes it unlikely that anyone would bother attacking Firefox extension developers is who cares about infecting all five people that still use Firefox?
do you enjoy sticking things in your bunghole? i sure do
I have yet to see a single phishing email that, when viewed in plain text mode, is remotely convincing. I still don't understand why people compromise so heavily for prettiness instead of privacy and security.
its too late do do anything they just have to be contained
[...] push out a malicious update that overlaid ads on top of web pages users were navigating.
That would explain why the ads on Slashdot are overlaying the content.
Always use your own bookmarks. Banks and everybody else need to stop sending links in emails.
How do they know what email address to send the phishing messages to? Is there a way to determine the author's email address from the Chrome store, or are they using information shared by the authors elsewhere?
Seems they are having some trouble. Well what do you expect when you hire 60,000 employees and don't bother to really check if they're good at their jobs.
But you check all those boxes on the diversity form. That clearly matters more.
Agreed - it would be just as likely as an app store like Apple or Google Play, or Microsoft's Windows 10 store, or Amazon apps (but keep reading). The *account* was what was compromised, not the app. When the account was compromised, the app could be modified.
At the heart of it is that Chrome's web store doesn't do safety-checking on extensions and apps for malicious content. You want to publish, it publishes. Instant. Done. Everybody gets the hacked version and everybody is at risk.
Chrome needs to do what Amazon does and at least have automatic reviews on things. Amazon in particular for their app store runs visual checks for some level of usability compliance, and programs automated tests. It takes me 6 hours between submission and publication for my app, but the security of my users is more assured.
"But remember, most lynch mobs aren't this nice." (H.Simpson)
-- Joe
Google's 2-Step Verification should be mandatory for developer accounts. End of discussion.
Send them all over to the middle east where they can fight with the sand nogs.
We dooomed!! Invader Zim's robot Gir https://www.youtube.com/watch?...
they asked me forever to update and i refused gee wonder why.....
they should have heeded my warnings and firefox is next....
use them to fertilize the cave bitches' empty wombs, left barren by the failing pink peenies of the melanin-deficient, sun-fearing pasty krakkkers.
which is basically Chrome's extension model but for Firefox.
Maybe you should read what the uBlock Origin maintainer thinks of the difference between the Chrome and Firefox implementations of WebExtensions. To quote him: "It baffles me that some people think Firefox is becoming a 'Chrome clone', it’s just not the case, it’s just plain silly to make such statement."
So who am I going to believe? An actual extension developer or some anonymous coward on Slashdot? I think I'll go with the developer.
Firefox is updating to an add-on model that's more stable, more secure, and not based off a giant hack from the early 90s.
"We need to get over this notion, that, for Apple to win... Microsoft must lose." - Steve Jobs, 1997