monty, this ticket is of course not meant to be a solution. The idea is to capture the details of corrupted packet just to have
more data to think where it comes from etc.
It may be not from a proxy, and could be from a mariadb plugin or other "X".

To remind you about audit plugin that was used to write into binlog file, and that was caught by reading into details of those messages.
Having more to the magic error in the error log also a note level message with the hexdump can't hurt obviously either.

I hope that clears your doubt.

Howdy Brandon!

Could you please check a simple few-liner.
I am all ears for anything to improve!

Andrei

Left a comment for consideration, and rpl.rpl_semi_sync_shutdown_await_slaves needs a fix to ignore the new error; otherwise looks good!