Deception/ API
D028F1 API

🔌 Honey Webhook

Canary webhook URLs planted in configs.

What it is

A webhook URL that points to an endpoint you control, planted in configs and scripts where real webhooks live. Attackers reuse webhooks to send data out or to test what they have found. Any request to the endpoint is the signal, and it carries the caller's address and request details.

Implementation requirements

Technologies

Application

ATT&CK coverage 5

TechniqueTacticStatusConfidenceTier
T1102
Web Service
Command & Control theoretical weak T2
↳ Detection point: the attack step itself touches the decoy
↳ Evidence (2 sources)

No evidence attackers use a found webhook as C2.

↳ Honey webhook as a C2 detector — industry-plausible only.
T1528
Steal Application Access Token
Credential Access theoretical moderate T4
↳ Detection point: the decoy fires at a later step of the attack
↳ Evidence (3 sources)

A stolen honey token fires when it is used, not when it is stolen.

T1567
Exfiltration Over Web Service
Exfiltration theoretical weak T3
↳ Detection point: the attack step itself touches the decoy
↳ Evidence (2 sources)

No evidence attackers exfiltrate to a webhook found in code; they use services they control.

T1567.004
Exfiltration Over Webhook
Exfiltration theoretical weak T3
↳ Detection point: the attack step itself touches the decoy
↳ Evidence (1 source)

No evidence attackers exfiltrate to a webhook found in code.

T1671
Cloud Application Integration
Persistence theoretical moderate T3
↳ Detection point: the attack step itself touches the decoy
↳ Evidence (2 sources)

Direct only when the attacker consents to, or adds credentials to, an existing decoy application; registering a new app touches no decoy.

Evidence