-
Notifications
You must be signed in to change notification settings - Fork 474
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Is Stream Cleaner legitimate? #171
Comments
That looks fishy af |
I am not going to base this analysis on the source code, because I don't know JS. Instead, the website:
|
I wouldn't recommend using it. Look at the manifest: Compared to the original: https://github.com/cleanlock/VideoAdBlockForTwitch/blob/master/chrome/manifest.json The manifest adds these additional permissions: Then look at these files: https://robwu.nl/crxviewer/?crx=https://chrome.google.com/webstore/detail/stream-cleaner/lehcglgkjkamolcflammloedahjocbbg&qf=background.js This requires the user to go to certain websites made by them or more likely a website with an ad made by them or their partners which will trigger their notification code. This is used to target people who are not familiar to trick them into some type of action. On operating systems such as Windows this looks quite official with the notifications popping up as system notifications. It isn't clear what type of notifications are sent as this needs to be paired with additional web page scripts. Does the Twitch ad blocking work? Yes. It uses the VAFT script: Google should do a better job of auditing their extensions. |
Stream Cleaner also shows |
stream cleaner works sooo good lol, ttv lol pro is awful i also decompiled stream cleaner source files and don't see anything alarming there at all. they modify the gql ad requests |
Link : https://chrome.google.com/webstore/detail/stream-cleaner/lehcglgkjkamolcflammloedahjocbbg
It seems to block ads fine, but some people have said it's a data farming extension? I've looked through all the javascript and nothing seems out of place.
The text was updated successfully, but these errors were encountered: