Link: https://socket.dev/blog/malicious-twitch-browser-extension

Threat Research Team identified a cross-store browser extension, “Twitch Enhanced Viewer | JeetBot,” that forwards each user’s live Twitch OAuth session token to proxy servers operated by a Russian commercial bot service. The extension ships on both the Chrome Web Store (extension ID pnhhdhhcadcjfckjhpmjneldiegbojfb, 30,000 users) and Firefox Add-ons (twitchenhancedviewer@example.com, 552 users). Both listings are live at time of writing.

And that's why you only use open-source addons if possible - less risk of this issue

A Google vetted source allowing code that compromises the end user? That's simply not possible. The developer had to provide an ID to publish the code. It MUST be safe! /s

There are closed sourced web browser addons‽
I swear all Manifest V3 & XPI are source readable.
Though Russian is a req..

Also, not sure how readable is a compressed, obfuscated source code on release.

nah, I earnest believe every person ðt installd ↓ just didn't boðer readŋ éðr code. Decompression is somθŋ every1 does. Ur internet connection can't work wo/it. I haven't botherd checkŋ if it has obfuscation.

Mate what is this language
I’ve made a v2 extension for Firefox, you CAN have obfuscated code in an extension by compiling it. HOWEVER, Mozilla requires you to submit the source code for any compiled/obfuscated code. Google has no reason not to catch it.
Compressed XPI packages can still be read afaik, they’re just JavaScript, CSS and HTML files at the end of the day.

Google has no reason not to catch it.

Apparently lying on threadiverse is also a requirement, seeing as you have no problems with it. JeetBot made no attempt to obfuscate their credential requiring addon, for other API means than to do both.

This was “Я верю в это.” No afterthought, no review.

Apologies, but I do not understand the argument you’re trying to make nor the part in my comment where I lied.

After Google created v3 manifests, all chrome addons MUST be readable. It's simply JS, HTML, & JSON in a ZIP.

I did not mention Google not having this measure (nor was I aware of it), I only stated what I knew. And this only proves my argument further anyway: Google has no reason not to catch it. (“it” being the malicious extension)
There were no lies in my comment but you jumped the gun, accused me of lying and were rude about it too.

Calling out misinformation is good, just please be politer.

Politeness is a ladder. The extension isn't still malicious: it does what it says. It just the tradeoff is getting your API credentials stolen. Calling twitchenhancedviewer “obfuscated” is pure disinformation, as we can both see both codes, Firefox's & Chrome’s.