logo
Forensic check

HTPBE_TRAILING_BYTES_AFTER_EOF

HTPBE_TRAILING_BYTES_AFTER_EOF appears on 0.2% 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

Structural Integrity

Unexplained data added to the file after it was finalised.

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

Marker profile

What HTPBE_TRAILING_BYTES_AFTER_EOF tells you

HTPBE_TRAILING_BYTES_AFTER_EOF is one of the named findings returned in modification_markers when a PDF is reported as modified. It belongs to the Structural Integrity group of checks. These checks look at whether the internal layout of the file is consistent with the file having been left untouched since it was finalised.

On 68.2% of the modified results that carry HTPBE_TRAILING_BYTES_AFTER_EOF it is the only marker. A result with this marker carries 1.5 markers on average. It is most often found together with HTPBE_IDENTITY_BLANKED, on 22.7% of these results.

Example API response

How it appears in a result

When a PDF is reported as modified, HTPBE_TRAILING_BYTES_AFTER_EOF 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_TRAILING_BYTES_AFTER_EOF"
  ],
  "creator": "Adobe Acrobat Pro DC",
  "has_incremental_updates": true,
  "page_count": 3
}

Full schema in the API reference →

Distributions

What ships alongside HTPBE_TRAILING_BYTES_AFTER_EOF

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

Common Producers

SAP NetWeaver 750 writes 31.8% of these results – and 25.9% of all modified results naming it carry this marker.

SAP NetWeaver 75025.9% of its modified31.8%

Common Creators

Form X_65_80 EN is the Creator on 31.8% of these results.

Form X_65_80 EN30.4% of its modified31.8%

Often found together with

HTPBE_IDENTITY_BLANKED sits next to HTPBE_TRAILING_BYTES_AFTER_EOF more often than any other marker.

Document origin

Institutional63.6%
Unknown22.7%
Consumer software13.6%

Creator → Producer pairs

Form X_65_80 EN → SAP NetWeaver 75031.8%

Confidence of the verdict

High100.0%

When these results were checked

July 202613.6%
August 20269.1%
September 202645.5%
October 202618.2%
November 202613.6%

Document length

1 page50.0%
2–5 pages45.5%
21–100 pages4.5%

File size

Under 100 KB72.7%
100 KB – 1 MB18.2%
1 – 5 MB9.1%

PDF versions

PDF 1.340.9%
PDF 1.418.2%
PDF 1.518.2%
PDF 1.713.6%

Year the document says it was created

202659.1%

Long tail

Notable observations

Smaller cuts of the results carrying HTPBE_TRAILING_BYTES_AFTER_EOF – 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
4.5%

Of files contain earlier saved revisions

Embedded JavaScript
13.6%

Of files contain JavaScript code

Embedded files
0%

Of files have attachments inside

Avg pages per document
3.4
Markers per result
1.5

Average number of markers on these results

Related checks

Other Structural Integrity checks

Checks from the same group. Each card links to its own reference page.

HTPBE_NAVIGATION_TABLE_MISMATCHInternal file structure showing signs of tampering
Share of modified0.5%
HTPBE_DECLARED_SIZE_MISMATCHFile layout altered after the file was finalised
Share of modified0.8%
HTPBE_PROPRIETARY_SIGNALAn additional integrity finding whose method is not disclosed
Share of modified0.7%

FAQ

HTPBE_TRAILING_BYTES_AFTER_EOF: common questions

What does HTPBE_TRAILING_BYTES_AFTER_EOF mean?

HTPBE_TRAILING_BYTES_AFTER_EOF is a named finding in an HTPBE? result: unexplained data added to the file after it was finalised. It is returned in the modification_markers list of a modified result and belongs to the Structural Integrity group of checks.

Does HTPBE_TRAILING_BYTES_AFTER_EOF 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_TRAILING_BYTES_AFTER_EOF?

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_TRAILING_BYTES_AFTER_EOF?

HTPBE_TRAILING_BYTES_AFTER_EOF appears on 0.2% 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_TRAILING_BYTES_AFTER_EOF?

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 Structural Integrity 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.

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