@rasmus
It's definitely a security concern to have sensitive credentials like your Twilio Account SID and Auth Token sent as plain text in payloads. These should be kept confidential to prevent unauthorized access to your Twilio account.
You should review your Twilio webhook configurations and ensure that you're not inadvertently passing these credentials in the URL or in the request body. Twilio's standard practice is to use HTTP POST requests with SSL to ensure data is encrypted during transmission, and credentials should not be included in the payload.
If you're using a Twilio Function or some other integration, double-check the code to make sure there's no line that adds these tokens to the payload. If you're unable to find the cause, I would recommend reaching out to Twilio support for further assistance.
For now, as a precaution, you might want to regenerate your Twilio Auth Token to prevent any potential misuse of the one that has been exposed. Please ensure that you update all your applications with the new token if you do so.
If you need assistance with contacting support or any other action, please let me know!