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
  • Use Cases
  • Metadata Viewer
  • Pricing

Developers

  • API Reference
  • GitHub/docs
  • Changelogv2.44.7

Resources

  • About
  • Blog
  • Comparisons
  • Legal & Imprint

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

Status

Algorithm v2.44.7

Tool profile

TargetStream StreamEDS

TargetStream StreamEDS 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
62%+13pp above baseline
Corpus baseline: 49%
Corpus share
0.26%
Share of all analyzed appearances
Modification rate
62%
+13pp above baseline
Role split
9%C/91%P
Creator vs Producer share of appearances

Corpus profile

How TargetStream StreamEDS shows up in HTPBE? corpus

TargetStream StreamEDS is one of the PDF-handling tools surfaced in the HTPBE? corpus. TargetStream StreamEDS appears predominantly as the Producer (91% of its occurrences) — i.e. on documents whose original Creator was a different application and that subsequently passed through TargetStream StreamEDS on the way out.

In the HTPBE? corpus the contextual signal we look for is a producer/creator mismatch: when TargetStream StreamEDS 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 TargetStream StreamEDS acts as Creator, 17% carry modification markers; on documents where it acts as Producer, 66% do. These are observed rates inside the HTPBE? corpus and should be read as base-rates, not as accusations against TargetStream StreamEDS or its users.

The signal
In the HTPBE? corpus the contextual signal we look for is a producer/creator mismatch: when TargetStream StreamEDS 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 TargetStream StreamEDS 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 · 9%
As Producer · 91%P
CAs Creator
  • Share of appearances
    9%
  • Modification rate
    17%
  • Avg file size
    145 KB
PAs Producer
  • Share of appearances
    91%
  • Modification rate
    66%
  • Avg file size
    268 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 TargetStream StreamEDS in the wild. All are merged into the same canonical profile.

TargetStream StreamEDS rv1.7.161 for Bank of America69.2%
TargetStream StreamEDS rv1.7.41 for Bank of America12.3%
TargetStream Technologies9.2%
TargetStream StreamEDS rv1.7.129 for StreamEDS for NCSECU6.2%
TargetStream StreamEDS rv1.7.188 for National Australia Bank3.1%

Why variants matter

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

Most common
TargetStream StreamEDS rv1.7.161 for Bank of America
69.2% of appearances
Variant spread
5 distinct strings
Long-tail share: 30.8%
Observed range
23.08.2021 → 13.08.2026

Distributions

What ships alongside TargetStream StreamEDS

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

PDF versions written

Most output is PDF 1.5 (65% of files where TargetStream StreamEDS is the Producer).

PDF 1.564.9%
PDF 1.717.5%
PDF 1.617.5%

Common Creators when TargetStream StreamEDS is the Producer

Bank of America sits upstream in 90% of cases — read this row as “what kinds of documents end up routed through TargetStream StreamEDS.”

Bank of America89.8%
TargetStream StreamEDS10.2%

Related profiles

Tools you’ll see next to TargetStream StreamEDS

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

C82% co-occurrence
Bank of America
Corpus share0.28%
Mod rate70%

Long tail

Notable observations

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

Avg pages per document
6.1
Oldest observed
23.08.2021 — about 5 years ago

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 →