OAST Correlation Markers
Readable token shapes for tying one callback to one campaign, request, field, variant, and trigger. Reserve an unsubmitted token for ambient-noise control and never place target secrets or user data in a hostname or path.
Use as a detection primitive
Readable token shapes for tying one callback to one campaign, request, field, variant, and trigger. Reserve an unsubmitted token for ambient-noise control and never place target secrets or user data in a hostname or path.
Identify the parser, sink, encoding, and expected non-vulnerable behavior before choosing a sample. Prefer non-destructive markers.
Use one readable case ID plus a random opaque suffix for every request, field, and variant. Keep one unsubmitted ambient-noise token. Put no secrets or target data in labels, paths, or queries. Redact at ingestion, never publish raw callback logs, and clean up controlled records after sufficient proof.
Recorded payloads
Confirm the sink and encoding context before use.
CAMPAIGN-CASE-REQUEST-FIELD-VARIANT.UNIQUE.oast.example- Expected signal
- Not verified for this generic template. Confirm the exact tool version and expected output in its official documentation before use.
- Negative control
- Define a known-safe or nonexistent target that should produce a meaningfully different result.
- Effect and bounds
- Unknown until flags and target are reviewed. Assume the command sends traffic or changes local state unless the tool documentation proves otherwise.
Confirm the sink and encoding context before use.
ssrf017-req88-avatar-direct.UNIQUE.oast.example/probe- Expected signal
- Not verified for this generic template. Confirm the exact tool version and expected output in its official documentation before use.
- Negative control
- Define a known-safe or nonexistent target that should produce a meaningfully different result.
- Effect and bounds
- Unknown until flags and target are reviewed. Assume the command sends traffic or changes local state unless the tool documentation proves otherwise.
Confirm the sink and encoding context before use.
bxss021-ticket-subject-render.UNIQUE.oast.example/pixel- Expected signal
- Not verified for this generic template. Confirm the exact tool version and expected output in its official documentation before use.
- Negative control
- Define a known-safe or nonexistent target that should produce a meaningfully different result.
- Effect and bounds
- Unknown until flags and target are reviewed. Assume the command sends traffic or changes local state unless the tool documentation proves otherwise.
Confirm the sink and encoding context before use.
bxss021-ticket-subject-exec.UNIQUE.oast.example/js- Expected signal
- Not verified for this generic template. Confirm the exact tool version and expected output in its official documentation before use.
- Negative control
- Define a known-safe or nonexistent target that should produce a meaningfully different result.
- Effect and bounds
- Unknown until flags and target are reviewed. Assume the command sends traffic or changes local state unless the tool documentation proves otherwise.
Confirm the sink and encoding context before use.
cmdi009-req14-host-semicolon.UNIQUE.oast.example- Expected signal
- Not verified for this generic template. Confirm the exact tool version and expected output in its official documentation before use.
- Negative control
- Define a known-safe or nonexistent target that should produce a meaningfully different result.
- Effect and bounds
- Unknown until flags and target are reviewed. Assume the command sends traffic or changes local state unless the tool documentation proves otherwise.
Confirm the sink and encoding context before use.
xxe012-import-body-parameter-entity.UNIQUE.oast.example/dtd- Expected signal
- Not verified for this generic template. Confirm the exact tool version and expected output in its official documentation before use.
- Negative control
- Define a known-safe or nonexistent target that should produce a meaningfully different result.
- Effect and bounds
- Unknown until flags and target are reviewed. Assume the command sends traffic or changes local state unless the tool documentation proves otherwise.
Confirm the sink and encoding context before use.
control017-unsubmitted.UNIQUE.oast.example/never-send- Expected signal
- Not verified for this generic template. Confirm the exact tool version and expected output in its official documentation before use.
- Negative control
- Define a known-safe or nonexistent target that should produce a meaningfully different result.
- Effect and bounds
- Unknown until flags and target are reviewed. Assume the command sends traffic or changes local state unless the tool documentation proves otherwise.
Attribution
Version history: normalized permanent page created 2026-08-20.