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.1

Resources

  • FAQ
  • Blog
  • Comparisons
  • Legal & Imprint

ยฉ 2024โ€“2026 TMI Iurii Rogulia ยท VAT ID: FI29845875 ยท Made in Finland ๐Ÿ‡ซ๐Ÿ‡ฎ

Status

Algorithm v2.23.1

Tool profile

Dropbox

Dropbox 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 13 appearances across the HTPBE? corpus.

Modification rate
62%+14pp above baseline
Corpus baseline: 48%
Total appearances
13
0.10% of corpus
Modification rate
62%
+14pp above baseline
Role split
100%C/0%P
Creator vs Producer share of appearances

Corpus profile

How Dropbox shows up in HTPBE? corpus

Dropbox is one of the PDF-handling tools surfaced in the HTPBE? corpus. Dropbox appears predominantly as the original Creator (100% of its occurrences) โ€” i.e. on documents that started life inside Dropbox 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 Dropbox 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 Dropbox acts as Creator, 62% 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 Dropbox or its users.

The signal
In the HTPBE? corpus the contextual signal we look for is a producer/creator mismatch: when Dropbox 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 Dropbox 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
  • Usage
    13
  • Modification rate
    62%
  • Avg file size
    300 KB
PAs Producer
  • Usage
    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.

Name fingerprints

Also goes by

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

Dropbox Sign76.9%
Dropbox23.1%

Why variants matter

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

Most common
Dropbox Sign
76.9% of appearances
Variant spread
2 distinct strings
Long-tail share: 23.1%
Observed range
7 Apr 2025 โ†’ 11 Feb 2026

Distributions

What ships alongside Dropbox

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

Common Producers when Dropbox is the Creator

Apache PDFBox writes 23% of these files โ€” that pairing is the Adobe-stack default for many institutional pipelines.

Apache PDFBox23.1%
iOS Print to PDF23.1%
iLovePDF7.7%

Related profiles

Tools youโ€™ll see next to Dropbox

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

P23% co-occurrence
Apache PDFBox
Appearances3
Mod rate33%
P23% co-occurrence
iOS Print to PDF
Appearances346
Mod rate68%
P8% co-occurrence
iLovePDF
Appearances584
Mod rate88%

Long tail

Notable observations

Smaller cuts of the Dropbox corpus โ€” useful context, but treat each row as a single data point rather than a strong signal.

Pages parsed
36
Oldest observed
7 Apr 2025 โ€” about 1 year 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 โ†’