Discord Webhook Support about canarytokens HOT 4 CLOSED

Hi @chrisreeves-

Thanks for raising this. This is an unfortunate side effect of Discord taking an unusual webhook format, and as a result not working with the standard output (though it's certainly interesting that the "/slack" inclusion actually makes it behave, I wouldn't have expected that).

We've had internal chatter in the past about adapting the webhook functionality to support Discord, but until now that hasn't come to anything. I'll raise this again and we'll get this working ASAP - so thanks again for the nudge!

from canarytokens.

This issue is stale because it has been open for 14 days with no activity.

from canarytokens.

Hey @quinn-thinkst thanks for the reply.

I found a way to do it by transforming the JSON payload being sent by using webhookrelay.com
They use lua for the transform, I'll leave the snippet I used to get it going (for others interested in this solution)

local json = require("json")

local body, err = json.decode(r.RequestBody)
if err then error(err) end

local token_type = body["token_type"]
local src_ip = body["src_ip"]
local time = body["time"]
local memo = body["memo"]

local message = "Canary triggered @ " .. body["time"] .. " src_ip: " .. body["src_ip"] .. " Source: " .. body["memo"] .. " Manage URL: " .. body["manage_url"]

-- Preparing Discord payload
local discord = {
    username= "OpenCanary",
    content= message
    }

local result, err = json.encode(discord)

-- Set modified request body
r:SetRequestBody(result)

from canarytokens.

Hey @chrisreeves-

I'm sorry this has taken a little while to get sorted (that's on me). Official support for discord webhooks is up and running now, so you can setup your tokens directly hooked into discord rather than needing an intermediary (but nice find on the relay - that's a nifty hack that should be usable for any case of an unsupported webhook).

Thanks again for raising this issue, and please do shout if you bump into any issues with the feature!

from canarytokens.