[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, body starts with title and ends in url, pattern-matching website in body, +3 more (589): Keto direct New Zealand by Joelletiteserow on graphicdesign.SE
[ SmokeDetector | MS ] Bad keyword with email in body, bad phone number in body, pattern-matching email in body, potentially bad keyword in body (240): GOOD WORK OF ILLUMINATI by Ken Smith on english.SE
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link following arrow in body, pattern-matching product name in body, +1 more (491): How to use Alpha Titan by Neeyaj on graphicdesign.SE
@Shree That pattern looks like it's already caught by Pattern-matching website in answer and Pattern-matching website in body; append -force if you really want to do that.
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, link at end of body, pattern-matching website in body, potentially bad ns for domain in body, +2 more (493): Flat belly fix Review by peaularmstrong on superuser.com
What if some person has access to someone else's StackExchange account (compromised credentials, open laptop, etc.) and goes ahead and posts something useless or even offensive garnering multiple downvotes and thereby negatively affecting that person's rep.
Can the original user be awarded his r...
@tripleee Yes. Both versions should be watched/blacklisted. For US numbers, they are commonly written without the 1 at the beginning, but spammers also write them with the 1. Watching/blacklisting one version does not detect the other.
> Bad phone number in body, potentially bad keyword in body ---------- Bad phone number in body - 5536 9137 5246 8484 found verbatim Potentially bad keyword in body - Position 17-36: 5536 9137 5246 8484