# Mime::Type::InvalidMimeType - Is this a hacking attack?

**URL:** <https://meta.discourse.org/t/mime-invalidmimetype-is-this-a-hacking-attack/185087>\
**Category:** Product Support\
**Created:** [April 1, 2021, 9:42am UTC](https://meta.discourse.org/t/mime-invalidmimetype-is-this-a-hacking-attack/185087 "2021-04-01T09:42:35Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)\
**Post date:** [April 1, 2021, 11:46am UTC](https://meta.discourse.org/t/mime-invalidmimetype-is-this-a-hacking-attack/185087/2 "2021-04-01T11:46:11Z")

</div>

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.

---

_[View the full topic](https://meta.discourse.org/t/mime-invalidmimetype-is-this-a-hacking-attack/185087)._