[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, potentially bad ip for hostname in body, potentially bad ns for domain in body, potentially bad keyword in body, +1 more (196): Kamagra 100 | sildenafil pills by latest pills on meta.SE (@Ollie)
@tripleee That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer Append -force to the command word(s) if you really want to add the pattern you provided.
@tripleee Already watched on line 40433 of watched_keywords.txt
@tripleee That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer Append -force to the command word(s) if you really want to add the pattern you provided.
@tripleee That pattern looks like it's already caught by Mostly punctuation marks in answer and Mostly punctuation marks in bodyThe regex contains an unescaped ".", which should be "\." in most cases. Append -force to the command word(s) if you really want to add the pattern you provided.
@tripleee It's impossible for this regex to ever match anything. You have [\W_]*+ followed with a character which is in the \W class, but all such characters will have always been consumed, so can't match. Such a formulation is in multiple places within this regex. For what it appears you want, you'd need something like h[\W_]*+t[\W_]*+t[\W_]*+p[\W_]*+s[\W_]*?:[\W_]*?/[\W_]*?/[\W_]*+w[\W_]*+w[\W_]*+w(?<!https://www)[\W_]*?\. However, that's 52 Total / 11 TP (21.15% TP) / 37 FP / 3 NAA, which doesn't seem like it has a high enough %TP to be worth watching, as it is. A slight modification h[\W_]*+t[\W_]*+t[\W_]*+p[\W_]*+s[\W_]*?:[\W_]*?/(?<!\\/)[\W_]*?/(?<!\\/)[\W_]*+w[\W_]*+w[\W_]*+w(?<!https://www)[\W_]*?\. results in 32 Total / 11 TP (34.38% TP) / 17 FP / 3 NAA (which still doesn't seem worth watching, but is better).
Overall, I'm not sure what you were really trying to detect, other than malformed URLs, or "stuff-ups". Unfortunately, those happen for everyone, from time to time, and aren't really unique to spam posts.
[ SmokeDetector | MS ] Blacklisted website in body, link at beginning of body, potentially bad ip for hostname in body, potentially bad keyword in body, potentially bad keyword in username (141): How to remove password from PDF? by akash ignissta on stackoverflow.com
> Potentially bad asn for hostname in answer, potentially bad keyword in answer ---------- Potentially bad asn for hostname in answer - yowhatsapp.org address 43.133.63.16 in ASN 132203 Potentially bad keyword in answer - Position 8-18: yowhatsapp
[ SmokeDetector | MS ] Potentially bad asn for hostname in body, potentially bad ns for domain in body, potentially bad keyword in body (3): CHUYÊN GIA DỤNG by nguyễn ngọc phú on sports.SE
[ SmokeDetector | MS ] Potentially bad asn for hostname in answer, potentially bad ns for domain in answer, potentially problematic ns configuration in answer, username similar to website in answer (72): How to send email via Django? by ProgramSpeaker on stackoverflow.com
@tripleee That pattern looks like it's already caught by Bad keyword in body and Bad keyword in answer Append -force to the command word(s) if you really want to add the pattern you provided.
@cigien That pattern looks like it's already caught by Bad keyword in body and Bad keyword in answer Append -force to the command word(s) if you really want to add the pattern you provided.
