TL;DR: 96.4% of fintech professionals see deepfake and synthetic identity fraud as a top concern, and nearly 30% reported incidents in the past year, Incode's survey found. Identity checks that trust device integrity and a live camera feed can be undermined together.
Editorial analysis by NHI Mgmt Group, based on content published by Incode: “How iPhone Jailbreaking Is Used to Commit Deepfake Fraud”.
Key questions
Q: Why does deepfake fraud become more effective on tampered phones?
A: Tampered phones let fraudsters control both the presentation layer and parts of the device environment.
Q: How can identity teams tell whether liveness checks are actually working?
A: Look for adversarial cases that still pass when motion is synthetic, partial, or replayed from a static image.
Q: What fails when identity checks trust a jailbroken or rooted device?
A: The failure is that the device can no longer be treated as an honest source of trust signals.
Practitioner guidance
- Strengthen device integrity checks Score jailbroken, rooted, emulator, and fingerprint-anomalous devices as high risk before allowing biometric proofing to continue.
- Validate camera capture integrity Detect virtual cameras, API interception, and feed substitution attempts so the verification flow can distinguish live capture from injected video.
- Correlate multiple fraud signals Combine device, camera, geolocation, and behaviour telemetry into one decision path so a passing selfie cannot override a compromised endpoint.
Bottom line: The core problem is not just deepfakes, but deepfakes delivered through devices that fraudsters can tamper with before verification begins.
Glossary terms: Jailbroken Device, Rooted Android Device, Camera Injection Attack, Multi-Angle Fraud
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Device trust assumptions collapse once the user controls the execution environment: The article shows that jailbreaking and rooting are not just policy violations, they invalidate the premise that the handset can be treated as a trustworthy verifier. When the attacker can modify the device, hide tampering, and present a synthetic camera feed, the identity system is judging evidence from an adversary-controlled endpoint. Practitioners should treat device state as part of identity assurance, not as a separate mobile-security concern.
A few things that frame the scale:
- Businesses report a 200% surge in attempted deepfake-aided wire fraud in Q1 2025 alone.
A question worth separating out:
Q: Should organisations block onboarding when device and camera signals conflict?
A: Yes. Conflicting signals usually mean the session cannot be trusted as a whole, even if one check passes. The right response is to pause automation, route the case for review, and require stronger evidence before account creation proceeds.
👉 Read our full editorial: Jailbroken devices are amplifying deepfake fraud in identity checks