Quantcast
Channel: Topic Tag: malware | WordPress.org
Viewing all articles
Browse latest Browse all 3861

John Morris on "[Plugin: Ad Blocking Detector] Malware trigger: sso.anbtr.com"

$
0
0

Thank you for bringing this to my attention. None of my sites have yet been flagged for this, but I'm sure it's coming.

The problem is people are targeting this plugin. They have created numerous problems and been pretty nasty in general. It happened before, on an old version (https://wordpress.org/support/topic/exadweseus-serving-malware?replies=4). It was one motivation for the massive update this plugin received recently.

One of the ad blocker detection mechanisms is an iframe that fools ad blockers into thinking it's an ad. The iframe is not supposed to point at anything real. It's an unregistered domain that points to a random file on the alleged server with advertisement keywords in the path. However, on three separate occasions, someone has purchased the unregistered domain chosen and served up malware through it.

The current version gets a randomized domain name periodically, so I thought that would be the end. However, it appears these... people... are willing to purchase the domain names, even if they are only good for a short time anyway. I will need to make more changes.

I'll work on an update A.S.A.P. In the meantime, you can stop this yourself by changing the "URL of the iframe" setting in the Ad Blocking Detector dashboard on the Advanced Settings tab. If you ignore the typo in the instructions I just found, you'll find instructions under the setting. Just give it a random domain and path. Preferably, one that does not exist. For example:

http://dfggsflwed21334s.me/adserver/adlogger_tracker.php
http://bnbxx889879878988x.li/ad/tracker/

Just something you think would make an ad blocker freak out, but that does not serve up malware.


Viewing all articles
Browse latest Browse all 3861

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>