Abusing Google Play Billing for fun and unlimited credits!
summary
Demonstrates that Google Play Billing allows local validation bypasses by reverse engineering real games Fruit Ninja, Doodle Jump and Snoopy Pop, using Apktool and bytecode edits, dnSpy to edit Unity security.dll and replacing package targets with the Billing ACK PoC to impersonate Google Play. Tests cover ~40 apps, with 25 successfully bypassed and only 5 performing server-side verification. Patches from Google do not prevent client-side tampering and the author’s demos generally work on-device despite occasional network hiccups modify bytecode to force verification true replace Google Play package with Billing ACK edit Unity security.dll with dnSpy
AI-written summary · about
chapters (10)
- 0:00Introduction and background
- 1:58What is Google Play Billing
- 9:50Known vulnerabilities history
- 13:12Client-side fixes limitations
- 15:00Case study Doodle Jump
- 19:13Case study Snoopy Pop
- 24:10Case study Fruit Ninja
- 29:17Developer security practices
- 30:46Research results and contact
- 31:51Q&A session
related talks
45mI just hacked your app!
36mI just hacked your app!
26mProtecting games and players by fighting abuse and piracy
45mI just hacked your app!
34mTesting In App Billing the Easy Way
07mI just hacked your app!
10mProtect your game's integrity on Google Play
28mProtecting Mobile Games Against Hackers, Crackers & Copycatters