Password-stealing Chrome extension smuggled on to Web Store; Researchers Demonstrated that Password-stealing Extensions are Still Possible with Manifest V3 (www.malwarebytes.com)
from Raisin8659@monyet.cc to technology@lemmy.world on 06 Sep 2023 07:13
https://monyet.cc/post/589344

Summary

Possible Takeaways / Other Details

#technology

threaded - newest

MakeItCount@lemmy.world on 06 Sep 2023 07:27 next collapse

At work we use crxcavator.io and the extension can only be installed on internal users devices if the total risk score is below 500 and if it does not ask for weird permissions

Diabolo96@lemmy.dbzer0.com on 06 Sep 2023 08:06 next collapse

This site is bogus. How the hell ublock origin and adblock Plus have the same score ? They should at least have a trusted add-ons based on if it’s open source or being recommended by reputable sites. I mean, Firefox audit some extensions and have a recommended tab. Use it and say recommended by Mozilla or something ?

Raisin8659@monyet.cc on 06 Sep 2023 08:47 collapse

Thanks. This could be a useful tool, but the scoring seems a bit “beta” at the moment. Still like the Recommended flair for Firefox better.

igorlogius@lemmy.world on 06 Sep 2023 07:41 next collapse

obligatory: eff.org/…/googles-manifest-v3-still-hurts-privacy…

Diabolo96@lemmy.dbzer0.com on 06 Sep 2023 08:08 next collapse

It was never about security

pastcoma@lemmy.world on 06 Sep 2023 08:41 next collapse

I’m not sure password managers like Last Pass or 1 Password could actually function without access to the DOM.

StudioLE@programming.dev on 06 Sep 2023 08:55 next collapse

They only require permission to write to the password field, they don’t necessarily need to read passwords. Although it does change the work flow for some users.

XTornado@lemmy.ml on 06 Sep 2023 09:01 next collapse

And it could work how it does on Android or similar where the browser has suggestions you can select to fill the field. Originally was for accessibility but it also works for password manger suggestions or any other sutofill. The extension would offer the suggestions to the browser and only the browser would read and actually do the input.

pastcoma@lemmy.world on 06 Sep 2023 10:04 collapse

I’m actually game for that idea, it would also make the browser responsible for parsing the many formats of html people use for structuring their input fields.

pastcoma@lemmy.world on 06 Sep 2023 10:02 collapse

Many password managers use a “save new” or “update” login credentials feature that watches for newly used passwords and asks if you’d like to save the credentials used.

That’s going to go away if you remove the read access. That said, maybe that’s not such a bad thing. Plenty of people will dislike losing that feature, however.

mathemachristian@lemm.ee on 06 Sep 2023 09:00 collapse

Most extensions won’t work without access to the DOM, since most extension need to interact with the webpage displayed. I mean what’s the point of being a browser extension if you can’t interact with the web page. The suggestion is to alert when a password field is accessed, maybe an extra permission an extension needs to access the value of a password field. Most extensions don’t need to, for example “dark reader” does not need to know any input field or text node value. So if it suddenly asked for permissions to read my password that would be very suspicious.

nekusoul@lemmy.nekusoul.de on 06 Sep 2023 09:26 collapse

The problem then becomes that extensions are still in control of everything else on the website: A malicious extension could simply hide or move the input field away and then create a new one in its place.

Personally, I don’t see how one could make extensions secure without severely crippling their functionality or turning it into a game of cat and mouse.

mathemachristian@lemm.ee on 06 Sep 2023 09:42 collapse

If an extension is blocked by the browser from accessing the value of any input field, text node content and recording keystrokes how can it then manipulate pages in a way that grants access to passwords?

The extension designer would have to actually create functionality which plausibly needs those permissions granted. Which would put a big dent in the “hello, if you want to monetize your extension put this code in it” type of scammers trying to gain access to that information via an extension that helps you zoom into images or whatever

nekusoul@lemmy.nekusoul.de on 06 Sep 2023 10:40 collapse

Then they could recreate their own input field by recreating their own “totally-not-an-input-field” with a canvas element and a bit of JS. Or, if that also gets blocked, just straight up redirect the user to a phishing site by replacing the login button or some other means. Plenty of people probably wouldn’t notice in time.

mathemachristian@lemm.ee on 06 Sep 2023 10:55 collapse

That’s a whole lot of effort compared to how they are able to phish now, which is launder their code by paying some (perhaps unsuspecting) extension developer to include an external dependency in their well-established extension.

Such effort as you’re describing would be harder to pull off, easier to spot and limit the victim pool significantly all at the same time.

MotoAsh@lemmy.world on 06 Sep 2023 12:13 collapse

The methods they described are very common hacking techniques once a site is compromised. They are not difficult nor more work than you’d expect, not out of the realm of normal work for a hacker with a site they can tweak.

bappity@lemmy.world on 06 Sep 2023 09:45 next collapse

it’s almost like they didn’t do it for security and just to make adblocking harder

UnknownQuantity@lemm.ee on 06 Sep 2023 12:53 collapse

Whaa? You crazy man? Surely that’s no possible…

excel@lemmy.megumin.org on 06 Sep 2023 16:41 collapse

Of course they can. Everyone knows that password managers exist.