logologo
  • How it works
  • Why It Matters
  • Statistics
  • Pricing
  • API
logologo
  • How it works
  • Why It Matters
  • Statistics
  • Pricing
  • 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.23.3

Resources

  • FAQ
  • Blog
  • Comparisons
  • Legal & Imprint

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

Status

Algorithm v2.23.3

Tool profile

Adobe PDF Library

Adobe PDF Library 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 340 appearances across the HTPBE? corpus.

Modification rate
73%+25pp above baseline
Corpus baseline: 48%
Total appearances
340
1.6% of corpus
Modification rate
73%
+25pp above baseline
Role split
0%C/100%P
Creator vs Producer share of appearances

Corpus profile

How Adobe PDF Library shows up in HTPBE? corpus

Adobe PDF Library is the embedded PDF-writing engine inside Adobe Acrobat, InDesign, Illustrator, and dozens of OEM applications licensed by enterprise software vendors. It is the canonical Adobe-stack producer for institutional documents — invoices, prospectuses, statements, regulatory filings.

In the HTPBE? corpus Adobe PDF Library appears predominantly on first-generation institutional output: documents whose Producer matches their Creator (e.g. InDesign + Adobe PDF Library) and whose XMP timeline shows a single CreationDate equal to ModDate. It is a low-signal producer for tampering on its own — what matters is whether a downstream re-saver shows up after it on the same file.

The signal
In the HTPBE? corpus Adobe PDF Library appears predominantly on first-generation institutional output: documents whose Producer matches their Creator (e.g.

Role in the workflow

How Adobe PDF Library 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 · 0%
As Producer · 100%P
CAs Creator
  • Usage
    0
  • Modification rate
    0%
PAs Producer
  • Usage
    340
  • Modification rate
    73%
  • Avg file size
    476 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 Adobe PDF Library in the wild. All are merged into the same canonical profile.

Adobe PDF library 17.0075.9%
Adobe PDF Library 23.35.3%
Adobe PDF library 18.003.5%
Adobe XML Form Module Library2.9%
Adobe PDF library 15.001.8%
Adobe PDF Services1.2%
Adobe PDF Library 26.1.1631.2%
Adobe PDF Library 15.01.2%
Adobe PDF library 8.001.2%
Adobe PDF Library 11.01.2%
Adobe PDF Library 17.00.9%
Adobe PDF Library 18.00.6%
Adobe PDF Library 25.1.510.6%
Adobe PDF Library 25.1.200.3%
Adobe PDF Library 24.2.130.3%
Adobe PDF Library 22.1.1170.3%
Adobe PDF Library 19.10.1230.3%
Adobe PDF Library 25.1.2110.3%
Adobe PDF Library 25.1.1080.3%
Adobe PDF Library 25.1.1920.3%
Adobe PDF Library 25.1.2310.3%
Adobe PDF Library 15.0; modified using iTextSharp 4.1.6 by 1T3XT0.3%

Why variants matter

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

Most common
Adobe PDF library 17.00
75.9% of appearances
Variant spread
22 distinct strings
Long-tail share: 24.1%
Observed range
25 May 2015 → 26 May 2026

Distributions

What ships alongside Adobe PDF Library

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

PDF versions written

Most output is PDF 1.6 (50% of files where Adobe PDF Library is the Producer).

PDF 1.649.5%
PDF 1.439.6%
PDF 1.35.6%
PDF 1.72.8%
PDF 1.52.5%

Common Creators when Adobe PDF Library is the Producer

Adobe Illustrator sits upstream in 83% of cases — read this row as “what kinds of documents end up routed through Adobe PDF Library.”

Adobe Illustrator82.6%
Acrobat PDFMaker5.3%
Adobe Acrobat5.3%
Adobe InDesign2.7%
Adobe LiveCycle Designer2.1%
Microsoft Word1.2%
Designer 6.30.9%

Related profiles

Tools you’ll see next to Adobe PDF Library

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

C82% co-occurrence
Adobe Illustrator
Appearances405
Mod rate84%
C5% co-occurrence
Acrobat PDFMaker
Appearances29
Mod rate86%
C5% co-occurrence
Adobe Acrobat
Appearances321
Mod rate53%
C3% co-occurrence
Adobe InDesign
Appearances12
Mod rate67%
C2% co-occurrence
Adobe LiveCycle Designer
Appearances10
Mod rate70%

Long tail

Notable observations

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

Digitally signed
3

PDFs carrying at least one digital signature

Pages parsed
1,140
Oldest observed
25 May 2015 — about 11 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 →