Topic starter
10/06/2026 12:13 am
TL;DR: Injection attacks targeting iOS devices surged 1,151% in the second half of 2025, deepfake incidents hit executive video calls, and Southeast Asia saw a 720% spike in Q3 2025 as AI-driven impersonation industrialized across enterprise workflows, according to iProov. Identity programmes now need continuous presence verification, not static assurance checks.
Editorial analysis by NHI Mgmt Group, based on content published by iProov: “iProov Issues Annual Threat Intelligence Report”.
By the numbers:
- Southeast Asia experienced a 720% spike in attacks in Q3 2025.
- 41% of organizations have experienced deepfake attacks targeting executives, according to Ponemon Institute research cited by iProov.
- 37% of cybersecurity leaders have encountered deepfake incidents during video calls, according to Gartner research cited by iProov.
Key questions
Q: How should security teams handle deepfake risk in identity workflows?
A: Security teams should treat deepfakes as a trust and verification problem inside identity workflows.
Q: Why do static identity verification controls fail against generative AI deception?
A: They assume the evidence of identity stays stable long enough to be trusted.
Q: What are the signs that deepfake-enabled fraud is slipping past verification controls?
A: Common signs include identity documents with internal inconsistencies, photos that do not match other identifying details, attempts to avoid live verification, claims of technical problems during checks, and suspicious account activity such as rapid transfers or payments to high-risk entities.
Practitioner guidance
- Strengthen presence verification for high-risk journeys Require continuous or step-up verification for payments, executive approvals, account recovery, and other workflows where a single impersonation can trigger material loss.
- Harden mobile capture paths Test for injection attacks, virtual camera abuse, and client-side tampering in the device and app paths used for identity verification.
- Reclassify video calls as trust-bearing workflows Add explicit identity checks to video-based approvals, support escalations, and executive interactions instead of treating them as informal human conversations.
Bottom line: Industrialized AI deception is eroding the reliability of static identity checks across mobile, video, and transaction workflows.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 1 day ago by NHI Mgmt Group
11/06/2026 1:55 am
Identity verification is becoming a runtime trust problem, not a point-in-time assurance problem. iProov’s findings show that synthetic identity can now survive long enough to pass ordinary checks and then influence downstream access or transaction decisions. That changes the governance question from whether a person was once verified to whether that verification still means anything at the moment of action. Practitioners should treat human presence as a continuously testable control, not a completed event.
A few things that frame the scale:
- 96% of organisations store secrets outside of secrets managers in vulnerable locations including code, config files, and CI/CD tools, according to Ultimate Guide to NHIs.
- 79% of organisations have experienced secrets leaks, with 77% of these incidents resulting in tangible damage.
A question worth separating out:
Q: Who is accountable when a deepfake impersonation bypasses identity controls?
A: Accountability sits with the organisation that allowed one trust signal to carry too much decision weight. Identity, fraud, and application owners all share responsibility when verification design permits synthetic presence to reach high-risk actions. Governance frameworks should map that responsibility before incidents occur.
👉 Read our full editorial: Industrialized AI deception is stressing identity verification controls
12/06/2026 3:29 am
Continuous presence verification is replacing static assurance as the real control boundary. Static identity checks assume the person or device in front of the verifier remains trustworthy for the duration of the transaction. Industrialized AI deception breaks that premise because the attack can be generated, adapted, and replayed faster than a point-in-time check can age. The practitioner implication is that identity assurance has to move from a single decision to an ongoing confidence model.
A question worth separating out:
Q: Should organisations use liveness checks, device integrity, or continuous presence verification?
A: They solve different parts of the same problem and are not interchangeable. Liveness checks help at capture time, device integrity helps protect the input path, and continuous presence verification helps prevent a convincing impostor from riding a trusted session into an approval or transaction.
👉 Read our full editorial: Industrialized AI deception is stressing identity verification controls
This post was modified 1 day ago by NHI Mgmt Group