@AdrianMole 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 This question [MS] doesn't appear to be TP to me. That's the original question content, so not vandalism. It's not a good question, and most SE sites definitely want to see something in the body, but the title appears to be an actual question (sort-of). It's definitely something that should be closed, IMO, but it doesn't seem like something SD should block.
Personally, I think it would be reasonable to have a system level block on that content, but it doesn't seem like the sort of thing that's in our remit.
@cigien 4 answers posted by this user in the last hour, all linking to their own article. Custom flagged. Remaining 5 hits on SE are by another user, also linking to their own articles without disclosure. Also custom flagged.
The quota_remaining property was not in the API response. Error: no method found with this name at 18:19:43 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions
[ SmokeDetector | MS ] Bad keyword in link text in body, potentially bad keyword in body, potentially bad keyword in title (72): bitcoin scam recovery by james on bitcoin.SE
