[ SmokeDetector | MS ] Potentially bad ip for hostname in answer, potentially bad ns for domain in answer, potentially bad keyword in answer, blacklisted user (74): Why DBAN cannot erase data on SSD by coinshen1 on superuser.com (@Ollie)
@tripleee That pattern looks like it's already caught by Blacklisted website in answer and Blacklisted website in body Append -force to the command word(s) if you really want to add the pattern you provided.
[ SmokeDetector | MS ] Bad ip for hostname in body, blacklisted website in body, potentially bad ip for hostname in body, potentially bad keyword in body, potentially bad keyword in title, +1 more (201): How much does BeLiv Blood Sugar Oil cost? by xofikus on stackoverflow.com
@SmokeDetector translation from Arabic: "I am being redirected I think they are terrorist criminals They have accessed my timeline in my Google account and tracked my home They are trying to physically kill me and my disabled child They are tech companies sponsored by NIST"
[ SmokeDetector | MS ] Bad keyword in answer, link at beginning of answer, potentially bad ns for domain in answer, potentially bad keyword in answer (124): URL rewrite in html by Pinky Mishra on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad keyword in answer, potentially problematic ns configuration in answer, blacklisted user (73): Games for Windows by playon 99 on askubuntu.com
[ SmokeDetector | MS ] Blacklisted username, offensive answer detected, pattern-matching website in answer, potentially bad keyword in answer, potentially bad keyword in username, +1 more (326): Print when textarea has overflow by FUCK.YOU BITCH on stackoverflow.com
