Yeah it is most likely a badly-behaved bot trying out different injection techniques.
I just checked our internal instance and it looks like we have /^Mime::Type::InvalidMimeType/ added as an ignore pattern in /logs/settings. Likely pr-welcome if someone would like to try stopping this kind of log at the source.