@tripleee Added s3698\.com to watchlist. However, the blacklists were not reloaded at this time. The most likely issue is another change was made on SD's master branch on GitHub and everything is waiting for CI to pass and MS to update the deploy branch. That could take a few to several minutes. If SD doesn't automatically reload the blacklists or automatically reboot after that time, then someone should investigate why that hasn't happened.
@VLAZ That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command word(s) if you really want to add the pattern you provided.
@VLAZ That pattern may be a North American number. If it is, please use a format which starts with an optional 1 followed by possible separator text and has the main number in the format 859-753-6221 where - could be a single alpha character or any [\W_]*+. Alternately, you can add the comment (?#IS NorAm) to the end of the pattern to force also using the alternate normalized form, or (?#NO NorAm) if it's not a North American phone number and it's incorrectly recognized as one. Perhaps try !!/blacklist-number 859-753-6221. Append -force to the command word(s) if you really want to add the pattern you provided.
@VLAZ A normalized version, {{'918597536221'}}, of that pattern is already on the number blacklist. You can use !!/bisect-number +918597536221 to determine which entries on the number lists match that pattern, which would tell you: Matched by +91]]-{{×8597536221 on line 2151 of blacklisted_numbers.txt: 918597536221 found normalized
@JeffSchaller That pattern may be a North American number. If it is, please use a format which starts with an optional 1 followed by possible separator text and has the main number in the format 938-426-0718 where - could be a single alpha character or any [\W_]*+. Alternately, you can add the comment (?#IS NorAm) to the end of the pattern to force also using the alternate normalized form, or (?#NO NorAm) if it's not a North American phone number and it's incorrectly recognized as one. Perhaps try !!/blacklist-number 938-426-0718. Append -force to the command word(s) if you really want to add the pattern you provided.
The fake support number spammers have turned their eye to https://salesforce.stackexchange.com/ and the site is being hammered with multiple spam posts per hour since several days back.
What is this and what can be done about it?
[ SmokeDetector | MS ] Bad keyword in body, pattern-matching website in body, potentially bad ip for hostname in body, potentially bad keyword in body (191): Why should we visit India? by varun tiwari on stackoverflow.com
@SmokeDetector Changed my feedback from tpu to just tp. The user seems to have legitimate posts beforehand. So, I'm erring on the side of "they didn't mean to spam". The post on the site has also been edited so now it looks a lot more like a "thanks" since it cites what another answer said. I'd NAA+del-vote it instead. But leaving the watch for the domain, just in case.
@tripleee thank you for the post you made on Salesforce. I think it's a great idea to let them know what's happening and how they can help. And perhaps even that they aren't alone against this.
@tripleee That pattern looks like it's already caught by Mostly non-latin body and Mostly non-latin answer Append -force to the command word(s) if you really want to add the pattern you provided.
[ 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 (147): BPP University assignment by Gradespire on stackoverflow.com
@VLAZ A normalized version, {{'009647824345176'}}, of that pattern is already on the number watchlist. You can use !!/bisect-number 009647824345176 to determine which entries on the number lists match that pattern, which would tell you: Matched by 009647824345176 on line 3694 of watched_numbers.txt: 009647824345176 found verbatim
@tripleee That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command word(s) if you really want to add the pattern you provided.
> Potentially problematic ns configuration in body, potentially problematic ns configuration in title ---------- Potentially problematic ns configuration in body - Suspicious nameservers: all IP addresses for documenthelps.com are in set {'65.108.66.125'} Potentially problematic ns configuration in title - Suspicious nameservers: all IP addresses for documenthelps.com are in set {'65.108.66.125'}
The fake support number spammers have turned their eye to https://salesforce.stackexchange.com/ and the site is being hammered with multiple spam posts per hour since several days back.
What is this and what can be done about it?
