|
|
|
|
|
by tobyhinloopen
2659 days ago
|
|
> There's no point to client-side JavaScript: The baddies just write JavaScript that rewrites basic objects using Object.defineProperty so that document.visibilityState always says so (and so on), or that lie to the visibility sensor. Or they just make a whole fake web browser that runs on a Server. You are in an arms-race, and verification companies simply can't/don't do a very good job. You cannot overwrite javascript properties in frames from another domain, right? Am I missing something? A fake webbrowser requires a lot of IP addresses. Wide-spread abuse seems hard to me, especially when combined with Google's hidden "I'm not a robot" thingy. |
|
You don't need to.
The SSP or publisher can slip the naughty JavaScript directly into the ad tag.
> A fake webbrowser requires a lot of IP addresses.
You may be surprised to learn there's a market for buying IP addresses, and they're cheaper than the revenue a bad actor can gain from using them.
There's also a lot of toolbars that embed some limited tunnelling functionality that they can then resell.
There's also a market for hacked DSL routers that you can tunnel through.