Mobile fraud no longer looks like a swarm of bots. Attackers now rent real-seeming phones by the hour, present device attestation that passes inspection, and replay requests that were legitimately signed. Approov, a provider of mobile app and API security, has responded with Approov 2027 (Version 3.7), a release that detects rented device farms, links each API request to the one device that created it, and verifies both in the cloud.
Approov CEO Ted Miracco said the attackers are operating real hardware at scale. “These are real banks of mobile phones that attackers are renting and manipulating to conduct scraping, fraud, and other API attacks,” he said. Because the devices are genuine, they can get past Apple’s App Attest and Google’s Play Integrity checks. “The problem is that a legitimate device can still be used for malicious purposes,” Miracco said. He added that Approov looks beyond standard integrity checks by spotting the signals tied to device farms and stopping their attacks at the API.
The Economics of Renting a Phone
Research published by Group-IB in March 2026 found that cloud-hosted Android phones can be rented for as little as $0.10 to $0.50 per hour, can present valid device attestation, and are used to open and run accounts for payment fraud. Device fingerprinting and behavioral scoring were never designed to stop an attacker who rents the genuine article.
Approov 2027 introduces several new capabilities:
- Device-farm and virtual-device detection: Leased device farms and virtualized devices used to pose as real customers are identified and blocked.
- Per-device request signing: Each device signs API requests with its own key, so a signature captured from one device can’t be replayed from another. This extends beyond token-based attestation by binding every request to its source device.
- New attack-tooling detections: Additional detections cover the latest hooking and instrumentation frameworks.
- Automated-abuse signals: Security teams get new indicators to help them block or rate-limit automated API use.
- Trusted time: A new SDK method gives apps a server-adjusted timestamp that doesn’t rely on the device clock.
- Stricter hardware attestation policy: Customers can opt to reject any Android device whose hardware-backed key attestation isn’t valid and unrevoked, with enforcement happening in Approov’s cloud rather than in the app.
Keeping the Trust Decision Off the Device
Many attestation products make or sign the trust decision inside the app, relying on code obfuscation or white-box cryptography to protect the keys. But anything shipped in an app can be examined on a device the attacker controls, and AI tooling is making that analysis quicker and cheaper. Approov’s patented attestation is instead verified in the cloud. No long-lived secret is stored in the app, and API keys are delivered only at runtime, after the app has proven itself.
“We believe cloud-native verification is why Approov offers the strongest protection available for mobile APIs,” Miracco said. “No control completely eliminates fraud. What attestation does is move the real cost of an attack from software, which scales for free, to hardware, which does not.” In his view, renting device farms was the attackers’ workaround, and the new release is the company’s answer to it.
Approov CTO Jae Hossell explained the distinction between the two approaches. “Token-based attestation proves the app was genuine when the token was issued,” he said. “Per-device signing proves that each request came from that same device. A signature lifted from one phone is worthless on another.” He added that a device in an attacker’s possession is the one place a secret can’t be kept, which is why Approov decides trust in the cloud.
Lessons From a State-Linked Adversary
Earlier this year, an Approov customer running high-value mobile APIs withstood a sustained campaign from a well-resourced adversary assessed to be state-linked, and its APIs stayed protected throughout. What Approov’s engineers learned about that adversary’s tooling has been built into this release for all customers. Approov has not disclosed the customer, its sector, or its location.
Next Up: AI Agents
Behavioral bot detection scores how a caller acts, but AI agents can mimic human behavior on demand, weakening that signal. Attestation poses a different question, Miracco said. “The question behind this release is what, exactly, is calling the API,” he said. “Enterprises are now asking the same question about AI agents, and per-device, per-request proof is the foundation we are building on to answer it.”
Availability
The Approov 2027 security rules were pushed to customer accounts over the air on November 16 and 17, 2026, and customers don’t need to take any action. The Version 3.7 SDK arrives on November 20, 2026, along with complete release notes covering performance improvements, use of Cloudflare’s global network from an app’s first launch, and new support for GrapheneOS.





