Hack installs tab allows you to see if your app was actually attempted to be hacked, injected with adware/malware, reverse engineered or modified in any way.
This is how it works: after any kind of modification (most likely it would be an automatic code or 3rd party SDK injection) your app with our SDK won’t launch. That’s it. It will simply crash or minimize itself. This is what we call a hack install.
In case of reverse engineering, attempt to remove your ads or our SDK or some other interference, an app should be compiled back manually. And it is unlikely to happen, it won’t build back, so the install won’t happen and we won’t be able to track it. However, there is small chance that someone does manage to pack it back and try to launch it, in that case we are unlikely to track such install either. Anyway, your app won’t be stolen and the “hacker” (there is a huge chance that it would be actially a bot-we will talk about it later in our blog) will be pretty much disappointed about it if s/he is a live being.
Normally, if someone does some sort of injection-they check if app works fine. If it doesn’t,then no sense in sending traffic to such app. That’s why you are most likely to occasionally see only very few number of hack installs. However,if the app was not tested after the modification,then you will be lucky to see real number of installs that were sent to your app.
For example here we can see that someone from China has been desperately trying to make app launch, most probably checking if our system actually works. As we can see, it does. However, in that case we can’t talk about some real traffic sent to a hacked app.
That’s how it all works from a users’ point of view.