@JeffSchaller I'll look at the others, but this one, and the one you just reported are undisclosed affiliation. I've added a comment on the first MS report.
Ok, both those are different accounts, but they're the same name, and link to the same website. They're definitely the same person.
@JeffSchaller Yeah, the other 2 posts don't seem to be spam. Should that watch be rejected then?
@Spevacus Oh, I totally missed that those posts are 5 years old. So the watch seems a bit pointless then.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in link text in body, potentially bad asn for hostname in body, potentially bad keyword in body, blacklisted user (237): What is SEO solution? by SEO SOLUTION on stackoverflow.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in link text in body, pattern-matching website in body, potentially bad ip for hostname in body, potentially problematic ns configuration in body (262): How to Fix 15841 Error in Computer by amitnd12345 on askubuntu.com
[ SmokeDetector | MS ] Few unique characters in body, no whitespace in body, potentially bad keyword in body, repeating characters in body (261): Получение текста by Алис Королев on ru.stackoverflow.com
@Mast That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; append -force if you really want to do that.
Bad keyword with email in answer - Keyword *Hacker* with email *look at CtesPersistence.txt* Potentially bad keyword in answer - Position 772-782: Sordum.org Potentially bad ns for domain in answer - sordum.org NS suspicious ns1.a2hosting.com.,ns3.a2hosting.com.,ns4.a2hosting.com.,ns2.a2hosting.com.
@VictorVosMottor I actually use that one when it fixes multiple links (and I know it would be wrong for 5 or more, but that's not likely to happen ...). What's the correct version for a single link?
@Someone_Evil Is the issue still current? You can check 'cred' with !!/whois admin, or just ping someone high up in the chain that's recently online. Like Makyen now.
