Injection Attack

An injection attack is an attack on a remote identity check in which false images or video are fed straight into the verification system, bypassing the camera. The system receives a digital file or stream that no lens recorded. Deepfakes are a common payload, because they can be generated to match a stolen identity.

Updated Reviewed by Tomas Zuoza, CEO of ZealiD

How does an injection attack work?

An injection attack works by replacing what the camera sees with content the attacker controls. A remote identity check expects a live image from the camera of a phone or a computer. The attacker inserts something else between the lens and the server that judges the image. The system then analyses a picture that was never in front of a camera.

There are several points of entry. Virtual camera software presents a video file to the operating system as if it were a webcam. An emulator imitates a phone on a computer, where the camera is whatever the attacker supplies. A modified app or a tampered phone can swap the feed inside the device. The attacker can also leave the device out altogether, sending prepared images straight to the provider's interface in the form the genuine app would use.

The injected content may be a stolen photo of a passport, a recording of the victim or a generated face. Once the set-up works, it can be repeated from one computer with a new identity each time.

What is the difference between an injection attack and a presentation attack?

A presentation attack happens in front of the camera. An injection attack happens behind it. In a presentation attack, a photo, a screen or a mask is held up to a genuine lens. The camera records a physical object, with the flaws a physical copy has: glare, flatness, visible edges. Liveness detection is built to notice those flaws.

In an injection attack the image arrives as clean digital data. A liveness check that studies only the picture may pass it. The two attacks therefore need different defences. One examines the scene. The other examines the route the image took.

Further reading

Why are deepfakes used in injection attacks?

Deepfakes are used in injection attacks because they give the attacker a face that moves on demand. A deepfake is an image, a video or a voice that machine learning has created or altered so that it appears to show a real person. Two kinds matter for identity checks. A face swap places the victim's face on the attacker's head in a video. A fully generated face shows a person who does not exist, to go with a forged document.

A stolen photo cannot blink. A recording cannot follow an instruction it did not expect. A face swap that runs in real time can do both, because the attacker performs the movement while the software redraws the face. Played on a screen in front of a camera, a deepfake still has to survive glare from the screen. Injected, it reaches the system at full quality.

How can an injection attack be detected?

An injection attack is detected by checking the route the image took as well as the picture itself. A method that resists injection combines several controls.

The first group of controls concerns the device. The app checks that it runs on a genuine phone, not an emulator. It checks that the operating system has not been tampered with, that the app is unmodified, that the image comes from the physical camera. A dedicated mobile app can make these checks more reliably than a web page, since a browser sees little of the hardware beneath it.

The second group ties the capture to the session. The server sends something unpredictable, such as a sequence of screen colours or an instruction, then looks for its trace in the video. A file prepared in advance will not contain it. A third group examines the content for the traces that generated video leaves. A fourth adds evidence that does not depend on the camera at all, such as reading the chip in a passport.

Does EU law address injection attacks?

EU law does not name injection attacks. It sets the result a method must achieve. Under Article 24(1a)(c) of the eIDAS Regulation, a qualified trust service provider that relies on its own identification method, such as a document check with a face capture, must ensure the identification of the person with a high level of confidence, which a conformity assessment body must confirm. Article 22(6) of the Anti-Money Laundering Regulation, which applies from 10 July 2027, names the means of verifying a customer's identity without mentioning the risk. Both sets of rules are set out under remote identity verification.

A method that accepts injected video cannot give a high level of confidence. Standards bodies, among them the European Committee for Standardization (CEN), have taken up the testing of injection attack detection.

A firm that builds its own check from uploaded photos carries the injection risk itself.

Related questions

Is an injection attack the same as a deepfake?

No. A deepfake is content. An injection attack is a way of delivering content. A deepfake played on a screen in front of a camera is a presentation attack. A stolen photo fed in through a virtual camera is an injection attack with no deepfake in it. The two are often combined, because injection delivers a deepfake at full quality.

Can an injection attack succeed on a live video call with an agent?

It can. A virtual camera can feed a video call tool in the same way, so an agent sees whatever the stream delivers. An agent can ask for unexpected movements, which makes a real-time face swap harder to sustain. Technical checks on the device are still needed alongside the agent's judgement. See video identification.

References

  1. Regulation (EU) No 910/2014 on electronic identification and trust services for electronic transactions in the internal market (eIDAS), Article 24(1a). European Union, consolidated version of 18 October 2024. eur-lex.europa.eu/eli/reg/2014/910/2024-10-18

  2. Regulation (EU) 2024/1624 on the prevention of the use of the financial system for the purposes of money laundering or terrorist financing (AMLR), Article 22(6). European Union, 2024. eur-lex.europa.eu/eli/reg/2024/1624/oj

  3. Technical specification on biometric data injection attack detection. European Committee for Standardization (CEN).

This article describes EU law: Regulation (EU) No 910/2014 (eIDAS) as amended in 2024 and Regulation (EU) 2024/1624 (AMLR), which applies from 10 July 2027. It names technical standards in general terms only. It explains the term in general and is not legal advice.

All glossary terms