# Contact Form Abuse

**URL:** <https://forum.kirupa.com/t/contact-form-abuse/196013>\
**Category:** random\
**Created:** [August 4, 2006, 3:48pm UTC](https://forum.kirupa.com/t/contact-form-abuse/196013 "2006-08-04T15:48:26Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jeff\_Wheeler](https://avatars.discourse-cdn.com/v4/letter/j/59ef9b/32.png) [@Jeff\_Wheeler](https://forum.kirupa.com/u/Jeff_Wheeler)\
**Post date:** [August 4, 2006, 3:48pm UTC](https://forum.kirupa.com/t/contact-form-abuse/196013/1 "2006-08-04T15:48:26Z")

</div>

Hmm… this is interesting. I got a message in my spam filter from “8441 [@] [nokrev.com](http://nokrev.com)” (ha, stupid catch-all), with this message:

> [@Message](#):
>
> Content-Transfer-Encoding: base64  
> Content-Type: text/plain  
> Subject:  
> to: [buletmann@aol.com](mailto:buletmann@aol.com)
> 
> 9c916f8d699fc83d808888a30963fa0d

It looks like they were trying to do some sort of header injection technique, and Django caught it (it does have automatic protection against said hack).

Do you think it was testing a vulnerability?