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
  • Why It Matters
  • Use Cases
  • Pricing

Developers

  • API Reference
  • GitHub/docs
  • Changelogv2.37.1

Resources

  • About
  • Blog
  • Comparisons
  • Legal & Imprint

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

Status

Algorithm v2.37.1

Tool profile

OmniPage

OmniPage 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
60%+12pp above baseline
Corpus baseline: 48%
Corpus share
0.10%
Share of all analyzed appearances
Modification rate
60%
+12pp above baseline
Role split
60%C/40%P
Creator vs Producer share of appearances

Corpus profile

How OmniPage shows up in HTPBE? corpus

OmniPage is one of the PDF-handling tools surfaced in the HTPBE? corpus. OmniPage splits its occurrences between Creator (60%) and Producer (40%) roles, meaning it sometimes originates documents and sometimes re-emits them after another tool created them.

In the HTPBE? corpus the contextual signal we look for is a producer/creator mismatch: when OmniPage 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 OmniPage acts as Creator, 100% 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 OmniPage or its users.

The signal
In the HTPBE? corpus the contextual signal we look for is a producer/creator mismatch: when OmniPage 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 OmniPage 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 · 60%
As Producer · 40%P
CAs Creator
  • Share of appearances
    60%
  • Modification rate
    100%
  • Avg file size
    134 KB
PAs Producer
  • Share of appearances
    40%
  • Modification rate
    0%
  • Avg file size
    373 KB

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.

Name fingerprints

Also goes by

Different version strings and spellings observed for OmniPage in the wild. All are merged into the same canonical profile.

OmniPage CSDK 1940.0%
OmniPageCSDK1940.0%
OmniPage CSDK 2120.0%

Why variants matter

The same tool publishes itself under 3 different metadata strings — version bumps, locale tags, build IDs. We canonicalize them so the corpus reflects one identity, not noise.

Most common
OmniPage CSDK 19
40.0% of appearances
Variant spread
3 distinct strings
Long-tail share: 60.0%
Observed range
17.08.2023 → 27.01.2026

Distributions

What ships alongside OmniPage

The PDF versions OmniPage writes when acting as Producer, and the other tools that appear in the same documents.

PDF versions written

Most output is PDF 1.7 (100% of files where OmniPage is the Producer).

PDF 1.7100.0%

Common Producers when OmniPage is the Creator

CopitrakCmdLn writes 67% of these files — that pairing is the Adobe-stack default for many institutional pipelines.

CopitrakCmdLn66.7%
CSDK2133.3%

Related profiles

Tools you’ll see next to OmniPage

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

P40% co-occurrence
CopitrakCmdLn
Corpus share0.01%
Mod rate100%
P20% co-occurrence
CSDK21
Corpus share0.00%
Mod rate100%
C40% co-occurrence
Scanner HP
Corpus share0.6%
Mod rate88%

Long tail

Notable observations

Smaller cuts of the OmniPage corpus — useful context, but treat each row as a single data point rather than a strong signal.

Avg pages per document
1.4
Oldest observed
17.08.2023 — almost 3 years ago

Secure your workflow

Create your account — API key on signup, free test environment on every plan.
From $15/mo. No sales call. Cancel any time.

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