G2VD: Generalizable AI-Generated Video Detection via Counterfactual Intervention and Causal Disentanglement

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

arXiv:2607.04607v2 Announce Type: replace-cross Abstract: Rapid advances in AI video generation pose increasing security risks and call for reliable detectors with strong cross-domain generalization. Although existing methods perform well under in-domain evaluation, their performance degrades substantially on unseen generators. A key reason is shortcut learning, where detectors rely on domain-specific bias rather than intrinsic forensic cues. To address this issue, we propose G2VD, a generalizable AI-generated video detection framework based on counterfactual intervention and causal disentanglement. First, G2VD introduces a counterfactual intervention pipeline (CFIPipeline) that constructs counterfactual samples through VAE-based reconstruction and subsequent frequency-domain and pixel-domain alignment, thereby weakening spurious correlations between domain-specific bias and authenticity labels. Building on this intervention, we further design a causal disentanglement classifier that combines two domain-anchored branches with complementary objectives and a constraint based on the Hilbert-Schmidt Independence Criterion (HSIC), encouraging the causal and non-causal representations to capture intrinsic forensic cues and domain-specific bias, respectively. Experiments across four public datasets demonstrate strong cross-domain performance and consistent gains over baseline methods. In the challenging GenVidBench setting, G2VD achieves over 90\% overall ACC, with improvements of 0.194 in F1 and 0.104 in AUC over comparable state-of-the-art methods, while using only 10\% of the …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://arxiv.org/abs/2607.04607
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.