logologo
  • How it works
  • Why It Matters
  • Statistics
  • Pricing
  • FAQ
  • API
logologo
  • How it works
  • Why It Matters
  • Statistics
  • Pricing
  • FAQ
  • API
HTPBE?

Structural PDF tamper detection API. Catches edits your KYC stack misses.

Product

  • How It Works
  • Use Cases
  • Metadata Viewer
  • Pricing

Developers

  • API Reference
  • GitHub/docs
  • Changelogv2.44.3

Resources

  • About
  • Blog
  • Comparisons
  • Legal & Imprint

© 2024–2026 TMI Iurii Rogulia · VAT ID: FI29845875 · Made in Finland 🇫🇮

Status

Algorithm v2.44.3

Tool profile

com.motorola.camera3 9.1.27.59

com.motorola.camera3 9.1.27.59 appears on both legitimate first-generation output and downstream re-save flows — context (the other tool on the same document) is what flips the signal.

Back to all statistics
Forensic verdict

Mixed signal

Based on this tool’s share of the HTPBE? corpus.

Modification rate
0%-49pp below baseline
Corpus baseline: 49%
Corpus share
0.10%
Share of all analyzed appearances
Modification rate
0%
-49pp below baseline
Role split
100%C/0%P
Creator vs Producer share of appearances

Corpus profile

How com.motorola.camera3 9.1.27.59 shows up in HTPBE? corpus

com.motorola.camera3 9.1.27.59 is one of the PDF-handling tools surfaced in the HTPBE? corpus. com.motorola.camera3 9.1.27.59 appears predominantly as the original Creator (100% of its occurrences) — i.e. on documents that started life inside com.motorola.camera3 9.1.27.59 rather than passing through it as a downstream re-saver.

In the HTPBE? corpus the contextual signal we look for is a producer/creator mismatch: when com.motorola.camera3 9.1.27.59 appears as the latest Producer on a document whose Creator was an institutional source (e.g. Adobe PDF Library, Microsoft Word, a banking back-end), the document was rebuilt or re-saved after its original creation. That mismatch is the marker — never the tool itself.

On documents where com.motorola.camera3 9.1.27.59 acts as Creator, 0% carry modification markers; on documents where it acts as Producer, 0% do. These are observed rates inside the HTPBE? corpus and should be read as base-rates, not as accusations against com.motorola.camera3 9.1.27.59 or its users.

The signal
In the HTPBE? corpus the contextual signal we look for is a producer/creator mismatch: when com.motorola.camera3 9.1.27.59 appears as the latest Producer on a document whose Creator was an institutional source (e.g. Adobe PDF Library, Microsoft Word, a banking back-end), the document was rebuilt or re-saved after its original creation. That mismatch is the marker — never the tool itself.

Role in the workflow

How com.motorola.camera3 9.1.27.59 shows up in metadata

Every PDF carries a Creator (the application that produced the original document) and a Producer (the engine that wrote the PDF). The same tool can appear in either slot, with very different modification profiles.

CAs Creator · 100%
As Producer · 0%P
CAs Creator
  • Share of appearances
    100%
  • Modification rate
    0%
  • Avg file size
    1.6 MB
PAs Producer
  • Share of appearances
    0%
  • Modification rate
    0%

How to read this

The Creator slot typically reflects where a document started life. The Producer slot reflects whatever wrote the bytes — and is the field that gets overwritten when a PDF is opened, edited, and saved by a downstream tool.

A higher modification rate as Producer than as Creator usually means the tool is acting as a re-saver on documents that originated elsewhere. A higher rate as Creator points to fragile workflows around the original authoring app.

Related profiles

Tools you’ll see next to com.motorola.camera3 9.1.27.59

Other tools that frequently share metadata with com.motorola.camera3 9.1.27.59 in the same documents. Each card links to its own forensic profile.

P100% co-occurrence
Adobe Scan
Corpus share0.24%
Mod rate28%

Secure your workflow

Create your account — check PDFs on the web or with an API key, both ready on signup.
From $15/mo. No sales call. Cancel any time.

Start Free — Close the Structural Fraud GapSee Pricing
Read API Docs →