Forensic check

HTPBE_REBUILT_FROM_LOCAL_SOURCE

HTPBE_REBUILT_FROM_LOCAL_SOURCE appears on 0.1% of modified results in our corpus. A marker is evidence about the file, not a judgement about the person who sent it.

Back to all checks
Marker profile

Document Assembly

Document reconstructed as a new file rather than produced as the original.

Share of modified results
0.1%
Frequency rank
#48
Among the 56 markers seen in modified results
Certain confidence
83.3%
Of results with this marker rated certain rather than high
Fires alone
16.7%
Results where it is the only marker found

Marker profile

What HTPBE_REBUILT_FROM_LOCAL_SOURCE tells you

HTPBE_REBUILT_FROM_LOCAL_SOURCE is one of the named findings returned in modification_markers when a PDF is reported as modified. It belongs to the Document Assembly group of checks. These checks look at whether a document reads as one coherent production or as pages and parts brought together from several places.

On 16.7% of the modified results that carry HTPBE_REBUILT_FROM_LOCAL_SOURCE it is the only marker. A result with this marker carries 3.5 markers on average. It is most often found together with HTPBE_DATES_DISAGREE, on 83.3% of these results.

Example API response

How it appears in a result

When a PDF is reported as modified, HTPBE_REBUILT_FROM_LOCAL_SOURCE is listed in modification_markers next to the verdict and its confidence. Each marker is a named, actionable finding – not a score.

GET /api/v1/result/{id}
{
  "id": "9f3a2c1d-8b47-4e6f-a012-3d5e7f890123",
  "status": "modified",
  "modification_confidence": "high",
  "modification_markers": [
    "HTPBE_REBUILT_FROM_LOCAL_SOURCE"
  ],
  "creator": "Adobe Acrobat Pro DC",
  "has_incremental_updates": true,
  "page_count": 3
}

Full schema in the API reference →

Distributions

What ships alongside HTPBE_REBUILT_FROM_LOCAL_SOURCE

The tools, formats and document traits that appear on the modified results carrying this marker. Shares are of those results.

Common Producers

Adobe PDF Library writes 50.0% of these results – and 1.0% of all modified results naming it carry this marker.

Adobe PDF Library1.0% of its modified50.0%

Common Creators

Adobe Illustrator is the Creator on 83.3% of these results.

Adobe Illustrator1.4% of its modified83.3%

Often found together with

HTPBE_DATES_DISAGREE sits next to HTPBE_REBUILT_FROM_LOCAL_SOURCE more often than any other marker.

Document origin

Consumer software83.3%

Creator → Producer pairs

Adobe Illustrator → Adobe PDF Library50.0%

Detected origin software

Adobe Illustrator66.7%

Confidence of the verdict

Certain83.3%
High16.7%

When these results were checked

July 202616.7%
August 202650.0%
October 202616.7%
November 202616.7%

Document length

1 page16.7%
2–5 pages83.3%

File size

100 KB – 1 MB33.3%
1 – 5 MB66.7%

Year the document says it was created

202350.0%

Long tail

Notable observations

Smaller cuts of the results carrying HTPBE_REBUILT_FROM_LOCAL_SOURCE – useful context, but treat each row as a single data point rather than a strong signal.

Digitally signed
0%

Of files carry at least one digital signature

Saved revisions
16.7%

Of files contain earlier saved revisions

Embedded JavaScript
0%

Of files contain JavaScript code

Embedded files
0%

Of files have attachments inside

Avg pages per document
3.2
Markers per result
3.5

Average number of markers on these results

FAQ

HTPBE_REBUILT_FROM_LOCAL_SOURCE: common questions

What does HTPBE_REBUILT_FROM_LOCAL_SOURCE mean?

HTPBE_REBUILT_FROM_LOCAL_SOURCE is a named finding in an HTPBE? result: document reconstructed as a new file rather than produced as the original. It is returned in the modification_markers list of a modified result and belongs to the Document Assembly group of checks.

Does HTPBE_REBUILT_FROM_LOCAL_SOURCE mean the document is fake?

No. A marker is evidence about the file, not a judgement about the person who sent it. It records that the file shows this pattern; it does not say why, and it does not assess what the document states. Read it together with the verdict and any other markers on the same result.

What should I do when a result contains HTPBE_REBUILT_FROM_LOCAL_SOURCE?

Ask the sender for the original file straight from the issuing system, or request a fresh copy from the issuer. Check whether the document went through a later step such as re-saving, merging or converting, and verify it with the issuer before relying on it for a decision.

How common is HTPBE_REBUILT_FROM_LOCAL_SOURCE?

HTPBE_REBUILT_FROM_LOCAL_SOURCE appears on 0.1% of the modified results in the HTPBE? corpus. The corpus consists of PDFs people chose to submit for checking, so it skews towards documents someone had a reason to doubt and is not a sample of all PDFs.

Where do I see HTPBE_REBUILT_FROM_LOCAL_SOURCE?

In the modification_markers list of the result returned by the HTPBE? API, and on the result page of a modified document. Other checks in the Document Assembly group are listed below on this page; all 63 checks are listed on the how-it-works page.

Secure your workflow

Create your account – check PDFs on the web or with an API key, both ready on signup.
No sales call. Cancel any time.