UPDATED: At the time this comment was originally posted, this was the best information I had before we did some more testing and realized it was a widespread issue. I'm keeping this comment public for now as I don't want it to look like I'm changing the past or anything, but reading further down will show the true details.
This is scheduled to be fixed in version 96.0.10
Original Post: Hey there! I don't have any good news on this one - all servers that I've previously seen that error on were compromised. If you'd like us to confirm that for you, please submit a ticket to our team so we can check.