Origin Lens: A Privacy-First Mobile Framework for Cryptographic Image Provenance and AI Detection

arXiv:2602.03423 · cs.CR, cs.CV, cs.CY, cs.HC · Submitted 2026-02-03 · Read on arXiv

Listen

Radio episode about this paper

Transcript

Introduction to the show: ident: Security Radio. Generated commentary on the latest security and cryptography papers.

Nadia: We're looking at the paper: "Origin Lens: A Privacy-First Mobile Framework for Cryptographic Image Provenance and AI Detection".

Elias: Here's the gist of the paper. Origin Lens presents a privacy-first mobile framework that performs cryptographic image provenance verification and AI detection locally on devices via a Rust/Flutter hybrid architecture because the proliferation of generative AI poses challenges for information integrity assurance, requiring systems that connect model governance with end-user verification.

Nadia: Framework Architecture The system employs a hybrid mobile architecture optimized for performance and memory safety, utilizing Rust for the core logic and Flutter for the user interface.

Elias: This separation allows the core logic to execute on-device below the processing boundary, leveraging Rust’s ownership model to prevent buffer overflows when parsing complex binary formats.

Nadia: The defense-in-depth strategy involves a four-layer pipeline to provide verification signals with decreasing confidence levels.

Paper summary: Nadia: So, we're talking about this paper, "Origin Lens: A Privacy-First Mobile Framework for Cryptographic Image Provenance and AI Detection." Basically, the whole idea is to tackle the problem that generative AI is creating—the issue with trusting information integrity because it's hard to verify where an image came from.

Elias: Right. The paper claims this framework does two main things: it verifies cryptographic image provenance locally on your device and it detects AI generation right there on the phone. It’s built using a Rust and Flutter hybrid architecture, which is key because they want the core logic to run on the device itself, not in some massive cloud server.

Priya: From a privacy standpoint, that local processing is important because it aligns with things like GDPR Article twenty-five on Privacy by Design <ref:2602.03423#pg1>. It means the sensitive data isn't being sent everywhere it doesn't need to go, which is a big step toward data minimization.

Nadia: Exactly. The paper presents this layered verification architecture, where you get signals at different confidence levels instead of just one big yes or no answer about whether an image is fake or not.

Elias: They use four layers for the image verification pipeline: first, cryptographic provenance parsing to check C2PA manifests and X.five hundred nine certificates against a local trust store, then heuristic metadata analysis for stuff like Stable Diffusion parameters in EXIF data, then watermark detection using an API, and finally contextual verification through an opt-in reverse image search to see if the image has prior attributions.

Priya: I'm curious about those signals. How do you weigh the confidence when you have a valid C2PA manifest versus just some pattern in the EXIF data or a watermark detection?

Nadia: That’s what they address by using a hierarchical confidence model, which helps distinguish between high-confidence things like a valid C2PA and lower-confidence signals like those heuristic metadata patterns or the reverse image search results.

Elias: The authors also look at the challenges of current standards, noting that while the C2PA standard enables decentralized provenance verification, most existing tools are still server-dependent.

Priya: So this paper positions its client-side approach as an alternative to those server-dependent systems? What does that mean for end users who just want to check a photo quickly?

Nadia: It means they’re aiming for speed and privacy on the device, with tests showing C2PA validation completes in under five hundred milliseconds for twelve megapixel images.

Conclusion: Elias: Looking at "Origin Lens: A Privacy-First Mobile Framework for Cryptographic Image Provenance and AI Detection," what I see is a framework designed specifically to solve the trust gap that's widening because of generative AI. The authors are really pushing for a system where you can verify content integrity without relying on external servers, which addresses the limitations they see in current C2PA tools.

Nadia: Yeah, and I think it matters because it puts the control back in the user's hands. They’re not just suggesting a fix; they’re proposing a complete mobile framework that handles both proving where an image came from and checking if AI made it, all while keeping things private on your device.

Priya: The implication for me is how practical this is. It moves the conversation away from just theoretical standards and into actual on-device implementation, which is where regulatory alignment like the EU AI Act becomes relevant for real-world compliance.

Elias: That’s right. They're not just talking about the technology; they are explicitly aligning their work with mandates like Article fifty and fifty-two of the Digital Services Act, which requires that platforms implement content moderation transparency <ref:2602.03423#pg1>.

Nadia: So, to sum it up for someone driving or walking: this paper proposes a privacy-first mobile tool that lets you check if an image has been tampered with or made by AI using local processing powered by Rust and Flutter, giving you multiple signals for different levels of certainty.

Priya: It’s about making sure that when we talk about verifying digital content, we're also thinking about how to do it in a way that respects user privacy right from the start.

Elias: And they've laid out their future work too, looking at things like lightweight neural networks for pixel-based detection and cross-jurisdictional standards as they move forward.

Nadia: It’s a lot of detail, but the main point is that we need these kinds of systems running locally to keep up with how fast generative AI is moving.

Frankfurt University of Applied Sciences · IMT Atlantique

cs.CR, cs.CV, cs.CY, cs.HC

Submitted: 2026-02-03

Updated: 2026-10-29

Comments: 8 pages. Peer-reviewed and accepted at the FIIR Workshop, The Web Conference 2026; the workshop was cancelled and the paper is not included in the proceedings. A separate, independent paper on Origin Lens appeared at ACM WebSci '26: doi:10.1145/3795513.3806658

Code: https://github.com/aloth/origin-lens

License: http://creativecommons.org/licenses/by/4.0/

Importance score: 90/100

The gist: Origin Lens presents a privacy-first mobile framework that performs cryptographic image provenance verification and AI detection locally on devices via a Rust/Flutter hybrid architecture because the…

Terminology

Summary

Origin Lens presents a privacy-first mobile framework that performs cryptographic image provenance verification and AI detection locally on devices via a Rust/Flutter hybrid architecture because the proliferation of generative AI poses challenges for information integrity assurance, requiring systems that connect model governance with end-user verification. p. 0

Where the paper says it

fr Abstract The proliferation of generative AI poses challenges for information integrity assurance, requiring systems that connect model governance with end-user verification. We present Origin Lens, a privacy-first mobile framework that targets visual disinformation through a layered verification architecture.

Framework Architecture

The system employs a hybrid mobile architecture optimized for performance and memory safety, utilizing Rust for the core logic and Flutter for the user interface. This separation allows the core logic to execute on-device below the processing boundary, leveraging Rust’s ownership model to prevent buffer overflows when parsing complex binary formats. p. 3

Where the paper says it

C System Architecture Details Origin Lens employs a hybrid mobile architecture optimized for performance and memory safety, separating the Dart/Flutter presentation layer from the Rust cryptographic core. The architecture provides several benefits: • Memory Safety: Rust’s ownership model prevents buffer overflows and use-after-free vulnerabilities when parsing complex binary formats.

The defense-in-depth strategy involves a four-layer pipeline to provide verification signals with decreasing confidence levels. p. 3
Where the paper says it

Pahl Accepted at TheWebConf ’26 Companion Supplementary Materials This supplement provides additional figures, architectural details, user interface screenshots, and regulatory context that support the main text. A Defense-in-Depth Verification Pipeline Origin Lens implements a four-layer defense-in-depth strategy for image verification, where each layer provides independent verification signals with decreasing confidence levels: Layer 1: C2PA Provenance.

Verification Pipeline Details

The defense-in-depth strategy consists of four layers for image verification, where each layer provides independent signals with decreasing confidence levels 1. Cryptographic Provenance parses JUMBF-embedded C2PA manifests, validates X. p. 3

Where the paper says it

A Defense-in-Depth Verification Pipeline Origin Lens implements a four-layer defense-in-depth strategy for image verification, where each layer provides independent verification signals with decreasing confidence levels: Layer 1: C2PA Provenance. The primary verification layer parses JUMBF-embedded C2PA manifests, validates X.

509 certificate chains against a local trust store, and computes SHA-256 hashes ensuring hard binding 2. p. 1
Where the paper says it

Origin Lens enforces hard binding validation [3]: SHA-256 hashes bind the manifest to image content—any modification invalidates the credential. Against spoofing, a local trust store validates certificate chains against known root authorities.

Heuristic Metadata analyzes EXIF/IPTC for generative model artifacts like Stable Diffusion parameters 3. p. 1
Where the paper says it

509 trust chains, and compute SHA-256 hashes ensuring hard binding [3, 16, 38]; (2) Heuristic Metadata—analyze EXIF/IPTC for generative model artifacts (e. , Stable Diffusion parameters); (3) Watermark Detection—detect imperceptible watermarks (e.

Watermark Detection detects imperceptible watermarks (e. p. 1
Where the paper says it

509 trust chains, and compute SHA-256 hashes ensuring hard binding [3, 16, 38]; (2) Heuristic Metadata—analyze EXIF/IPTC for generative model artifacts (e. , Stable Diffusion parameters); (3) Watermark Detection—detect imperceptible watermarks (e.

g., Google SynthID) via API 4. p. 1
Where the paper says it

, Stable Diffusion parameters); (3) Watermark Detection—detect imperceptible watermarks (e. , SynthID) via API [4, 13, 14]; (4) Contextual Verification—opt-in reverse image search for prior attributions.

Contextual Verification involves an opt-in reverse image search for prior attributions. p. 1
Where the paper says it

, Stable Diffusion parameters); (3) Watermark Detection—detect imperceptible watermarks (e. , SynthID) via API [4, 13, 14]; (4) Contextual Verification—opt-in reverse image search for prior attributions.

Security and Threat Mitigation

Threat modeling using STRIDE analysis identified risks such as Manifest Stripping, where adversaries remove C2PA metadata during redistribution, and Certificate Spoofing, where attackers forge X.509 certificates to inject false provenance claims. p. 1

Where the paper says it

At the Verification Pipeline layer, we identify two primary risks: (1) Manifest Stripping (Tampering)—adversaries remove C2PA metadata during redistribution, a known limitation of content credentials [3]; and (2) Certificate Spoofing (Spoofing)— attackers forge X. 509 certificates to inject false provenance claims.

Mitigations include enforcing hard binding validation via SHA-256 hashes and validating certificate chains against a local trust store to counter spoofing. p. 1
Where the paper says it

Origin Lens enforces hard binding validation [3]: SHA-256 hashes bind the manifest to image content—any modification invalidates the credential. Against spoofing, a local trust store validates certificate chains against known root authorities.

The analog hole, or screen capture, is addressed through heuristic metadata and watermark detection as secondary signals when manifests are absent. p. 1
Where the paper says it

The analog hole—screen capture—circumvents cryptographic provenance [14, 29]. We address this through defensein-depth: heuristic metadata and watermark detection provide secondary signals when manifests are absent.

Regulatory Alignment

Origin Lens aligns with emerging EU regulations by implementing on-device processing for core verification, adhering to GDPR Article 25 regarding Privacy by Design and data minimization It also addresses the EU AI Act's mandates for machine-readable provenance metadata through C2PA manifest parsing and AI generation detection via metadata. Furthermore, the framework incorporates Rust memory safety for security-by-design requirements under the Cyber Resilience Act. p. 6

Where the paper says it

Pahl Accepted at TheWebConf ’26 Companion Table S2: Regulatory alignment of Origin Lens features. Regulation Relevant Requirements Origin Lens Alignment EU AI Act (2024/1689) Articles 50, 52: Machine-readable provenance for AI-generated content C2PA manifest parsing and AI generation detection via metadata GDPR (2016/679) Article 25: Privacy by Design; Article 5: Data minimization On-device processing; no server transmission for core verification Cyber Resilience Act (2024/2847) Security-by-design for digital products Rust memory safety; X.

Evaluation and Uncertainty Communication

On iOS devices, C2PA validation completes in under 500ms for 12MP images, with EXIF parsing taking less than 50ms. The system communicates results using a traffic light UI where green indicates a valid C2PA manifest from a trusted root The framework implements a hierarchical confidence model, distinguishing between high confidence (valid C2PA) and lower confidence signals like EXIF patterns or opt-in reverse image search. p. 1

Where the paper says it

Communicating uncertainty is a known challenge [10]. Origin Lens implements a hierarchical confidence model: high (valid C2PA with trusted root), medium (EXIF patterns, watermarks), and low (opt-in reverse image search requiring user interpretation).

Limitations include the dependency on ecosystem adoption and the evolving nature of generative models affecting heuristic detection effectiveness. p. 1
Where the paper says it

Limitations. C2PA effectiveness depends on ecosystem adoption [3].

Conclusion and Future Work

Origin Lens provides an open-source, privacy-first implementation for on-device image provenance verification, complementing platform-level mechanisms Future work is planned to include lightweight neural networks for pixel-based detection, privacypreserving federated aggregation, and cross-jurisdictional provenance standards. The research invites experts to participate in a survey on verification practices. p. 2

Where the paper says it

Pahl Accepted at TheWebConf ’26 Companion lightweight neural networks for pixel-based detection, privacypreserving federated aggregation, and cross-jurisdictional provenance standards. As our research continues, we invite experts to participate in our survey on verification practices: https://github.

Green — the paper says it, and the page is printed. Red — no passage carries it, so treat that sentence as unverified. The same check runs on your own text: check a summary against its source, $5.

Improvements for AI systems

  1. Privacy-First On-Device Verification for Image Integrity

The improved system can perform cryptographic image provenance verification and AI detection locally on a mobile device using a Rust/Flutter hybrid architecture, ensuring Privacy by Design by processing data entirely on-device to avoid server dependencies or data harvesting concerns.

  1. Layered Defense-in-Depth for Content Authentication

The system implements a four-layer pipeline: Cryptographic Provenance (Layer 1), Heuristic Metadata (Layer 2), Watermark Detection (Layer 3), and Contextual Verification (Layer 4). This allows the AI system to provide graded confidence indicators by combining multiple signals, such as cryptographic provenance, generative model fingerprints, and optional retrieval-augmented verification.

  1. Automated Regulatory Compliance for AI Content

The framework directly addresses regulatory requirements by implementing features aligned with the EU AI Act and DSA. Specifically, it provides machine-readable provenance metadata for AI-generated content via C2PA parsing and supports content moderation transparency through on-device detection mechanisms.

  1. Mitigation of Adversarial Manifest Stripping

The system enhances robustness against content tampering by enforcing hard binding validation, where SHA-256 hashes bind the manifest to image content, ensuring that any modification invalidates the credential. This prevents adversaries from removing C2PA metadata during redistribution.

  1. Memory Safety in Cryptographic Processing

By utilizing Rust for the core logic, the improved system leverages Rust's ownership model to mitigate memory corruption risks when parsing complex binary formats, directly addressing vulnerabilities identified at the Cross-Language Bridge layer.

Abstract

The proliferation of generative AI poses challenges for information integrity assurance, requiring systems that connect model governance with end-user verification. We present Origin Lens, a privacy-first mobile framework that targets visual disinformation through a layered verification architecture. Unlike server-side detection systems, Origin Lens performs cryptographic image provenance verification and metadata-based AI detection locally on the device via a Rust/Flutter hybrid architecture. Our system integrates multiple signals - including cryptographic provenance, generative-model metadata and watermarks, and optional retrieval-augmented verification - to provide users with graded confidence indicators at the point of consumption. We discuss the framework's alignment with regulatory requirements (EU AI Act, DSA) and its role in verification infrastructure that complements platform-level mechanisms.

Sources

Related papers