How do MMPs actually catch SDK spoofing and fake in-app events?
One source has normal-looking installs and even some purchase events, but day-two retention is almost zero. Someone mentioned SDK spoofing. How does that even get detected?
Answer from the Linkrunner team
SDK spoofing is when fraudsters record a real SDK's traffic, then send fabricated install and event requests straight to the MMP's servers, paired with their own clicks so they get credited. No device, no user, and sometimes fake purchases to pass quality checks. The main defence is request signing: the SDK signs each request with a secret built into genuine builds, and unsigned requests get rejected or flagged. Other signals are data-centre or Tor IPs, click and install IPs that don't match, impossible device and OS combinations, and what you're seeing: near-zero retention and events that stop abruptly. Turn on signing in every version you ship, withhold postbacks for flagged installs so networks stop optimising toward them, and raise it with the network. Fraud Control on Linkrunner: https://linkrunner.io/fraud-protection
More on this: linkrunner.io/glossary/what-is-sdk-spoofing