New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lyrics Window plugin: prevent malicious ads from running #1927

Closed
CreamyCookie opened this Issue Apr 28, 2016 · 2 comments

Comments

Projects
None yet
2 participants
@CreamyCookie
Contributor

CreamyCookie commented Apr 28, 2016

So, I have no idea if this is even possible to fix, but when I returned to my PC I saw this:

web cancer

(I don't even have a Nexus 5.)

After clicking okay, the browser of the lyrics window showed me a phishing page that basically said something similar to the above Javascript messagebox. It also used the Google logo to make it seem official. I sadly couldn't make a screenshot of that, because the song was over before I had done it. The song was "J'ai Dormi Sous L'Eau" and it has a lyrics wiki page.

The only explanation I have is that some advertisement code from lyrics wikia or the site itself has been hijacked. When I now play that song, it doesn't happen, so my guess is that it's just one advertiser.

@lazka lazka closed this in aff0edc May 1, 2016

@lazka

This comment has been minimized.

Member

lazka commented May 1, 2016

Uh, the lyricswiki page is horrible now; lots of big and slow ads...

@CreamyCookie

This comment has been minimized.

Contributor

CreamyCookie commented May 1, 2016

Yeah, I have no problem with text ads that don't need JavaScript and don't track one either. But these ads are not only sometimes malicious, they also waste your time in many different ways (slowing down the browser / loading the site, being distracting and (sometimes) having to click them away).

Anyway, it would be cool if an organization like Wikimedia could provide a site for lyrics (without having to pay royalties and obviously without ads).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment