TL;DR: Legitimate mobile apps can still be abused for ticketing and betting fraud through exposed secrets, API trust failures and token theft, Approov reports. Runtime assurance and short-lived secrets become necessary when backend trust can be replayed from a real app.
Editorial analysis by NHI Mgmt Group, based on content published by Approov: “Sold-Out Stadiums, Stolen Wallets: Why Mobile Sports and Betting Apps Are the Scam Frontier This Season”.
Key questions
Q: Why do legitimate mobile apps still get abused for fraud?
A: Because app store legitimacy does not protect the runtime environment.
Q: What are the signs that a mobile app’s anti-tamper controls are failing in practice?
A: Warning signs include keys that can be traced through obfuscated code, runtime hooks that still reveal sensitive flows, and protections that only slow down analysis rather than stop it.
Q: What breaks when a mobile app still contains secrets or tokens in its binary?
A: The app stops being a thin client and becomes a reusable credential store.
Practitioner guidance
- Eliminate embedded mobile secrets Remove API keys, tokens and credentials from the app binary and issue only runtime secrets to verified app instances.
- Bind backend trust to app attestation Require evidence that the client is a genuine, untampered app before granting access to ticketing or betting APIs.
- Treat token theft as a session design problem Reduce bearer token lifetime, limit scope and revoke sessions aggressively when misuse or device compromise is suspected.
Bottom line: The core risk is that a legitimate mobile app can still be compromised through its secrets, APIs and sessions even when the download path was legitimate.
Glossary terms: Zero-Secrets Architecture, Runtime Secrets Protection, Certificate Pinning, Runtime Application Self-Protection
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Mobile app runtime trust is now the real control boundary: the old assumption that store review equals safety no longer holds when the app carries the credentials attackers want. A legitimate binary on an untrusted device can be reverse engineered, instrumented or repackaged, which means governance has to move from distribution approval to runtime assurance. The practical conclusion is that mobile apps need controls that verify the app instance before releasing anything valuable.
A question worth separating out:
Q: How should security teams balance pinning with certificate rotation in mobile apps?
A: Use dynamic pinning rather than hardcoded static pins wherever possible. That lets the trust set change without forcing an app update, while still preventing interception. The goal is to preserve channel integrity without creating self-inflicted outages when certificates rotate, expire or need to be revoked.
👉 Read our full editorial: Mobile app fraud now targets secrets, APIs and tokens