@Dharman From what's happening, it sounds like that userscript changes what's in the .content to the point where FIRE doesn't parse the URL out of the HTML.
Yes it does seem they set up an account under the name "the4kman" and they do have the Flagger role.
Those posts were flagged via a spam wave. It's possible that their account was used to flag despite them not having autoflag conditions set because they 1) Are a registered user, and 2) Have the flagger role.
But I will not assert that without knowing if that's how it works.
cc @Makyen Might need someone with some expert knowledge :D
Usually matching on word boundaries is what you want (see, e.g., Scunthorpe problem). It's just when your pattern starts or ends with something that's not a letter or number (or underscore) that you run into that.
[ SmokeDetector | MS ] Link at beginning of answer, potentially bad asn for hostname in answer, potentially bad ns for domain in answer (36): Does Simics use SMM? by user17523590 on stackoverflow.com
@CodyGray feel free to blacklist immediately any new phone numbers related to this spam wave, I don't think it makes any sense to give them any benefit of doubt
Hm, OK. I wasn't 100% sure that this was the same spam wave, and there's only ever been 1 hit (I think?), so I was waiting until I at least saw a second one.
[ SmokeDetector | MS ] Bad ip for hostname in body, bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching product name in body, +3 more (493): What is the Cannery CBD Oil UK price? by suniooborida on superuser.com (@Ollie)
@CodyGray That pattern looks like it's already caught by Bad keyword in answer and Bad keyword in bodyThe regex contains an unescaped ".", which should be "\." in most cases. Append -force to the command if you really want to add this pattern.
@CodyGray That pattern looks like it's already caught by Mostly non-latin answer and Mostly non-latin body Append -force to the command if you really want to add this pattern.