Identifying Advertising Fraud and Abuse
summary
Identifies three high‑impact fraud patterns and concrete detection signals: INSTALL_REFERRER broadcast abuse causes install attribution fraud — replace with the Play Store install referral HTTP API; programmatic clicking uses APIs like dispatchTouchEvent with fabricated X/Y coordinates and methods named “autoclick” or “delayClick”; disruptive ads use boot completed receivers + AlarmManager/PendingIntent, hide from launcher and dynamically swap inventory. Testing notes: analyze manifests for install referrers, run real-device installs (not emulators or common VPN/cloud ASNs), let apps sit to observe cloaked behavior.
AI-written summary · about
chapters (10)
- 0:00Introduction to ad fraud
- 1:29Why ad fraud matters
- 2:53Install attribution fraud
- 7:07Programmatic clicking fraud
- 9:55Disruptive ad behavior
- 13:32Spoofing and arbitrage schemes
- 17:22Cloaking techniques in adware
- 21:37Testing SDKs for fraud
- 25:13Avoiding fraudulent SDKs
- 25:53Q&A and closing
related talks
40mReversing Fraudulent Apps
19mWhich mobile fraud solution is right for you?
45mModern fraud trends in RTB
30m"Latest Android threats and their techniques"
36mFraud in mobile applications: how to define and detect
43mHow to Stop Cheat Sellers Damaging IAP and Ad Revenue.
26mAPI Abuse - Comprehension and Prevention
44mAuditing Your APKs Like a Black Hat Hacker