📜 ⬆️ ⬇️

Tricky way to drain mobile traffic

Webmasters - owners of sites with a little bit decent attendance for certain have repeatedly received messages like this:
!       *****.ru.    5%  20%      .    .         !  100%  WAP .     25$  1000  . ... PS    .      .     ! 


Usually, the essence of such an offer comes down to adding literally a few lines to the .htaccess site, thanks to which all mobile traffic will be redirected to a certain partner site.

I received such an offer, too, repeatedly. At first, he answered with a polite refusal, and then simply began to leave unanswered.

Along with this, but, unfortunately, much less often, there are also offers to place advertising banners. Occasionally from direct advertisers, but increasingly from agencies. And recently, a similar proposal came up for placing a graphic banner on one of the free sites on the site. And here the quick-witted reader probably already began to guess how this relates to the letter from the first paragraph.
')
But at the first moment I did not suspect a dirty trick and decided to place the JS code on the site. Well, posted and forgot about it. And after a while I received a message from one of the site users that the site had stopped opening from a mobile phone. During the correspondence with him, it turned out that instead of the site, a kind of stub was opened, offering to update the Flash version. At first I decided that Flash is really required to display a banner, but decided to clarify which device the user is trying to access the site from. And it turned out that this is not even a smartphone, that is, about any Flash and could not be.

Already at that moment I began to have vague doubts. And I, armed with the plugin User Agent Switcher for FireFox, putting in its settings "iPhone 3.0" I go to my website and find a redirect to the very stub offering to update the version of the Flash player. Further, already by scientific tyke, that is, by alternately disabling ad units on the site, we managed to find out which of the codes caused this behavior.

Purely from a technical point of view, everything was done very primitively. For “normal” browsers, a nice picture was given with a link to a completely decent partner site, and for all mobile browsers such simple JavaScript code was added at the end:
 setTimeout(function(){window.location='http://*****.net/?a=t2d4w294z215y2w4u2w423m254l2u266r2z274w2e423d413e4y2'},1000); 

Webmasters, be vigilant and learn from the mistakes of others! If after reading this article, someone has any suspicions, I recommend using the above-mentioned plugin and checking the operation of your sites with the mobile User-agent in it.

Source: https://habr.com/ru/post/151595/


All Articles