[ SmokeDetector | MS ] Bad ip for hostname in body, bad keyword in body, bad keyword with email in body, bad phone number in body, blacklisted website in body (455): how to make pvc patches? by GSPVC Patches123 on mathoverflow.net
Recovered from ValueError: netloc 'Draft.js：WYSIWYGエディタのページ分割' contains invalid characters under NFKC normalization
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, body starts with title and ends in url, link at end of body, potentially bad ns for domain in body, +2 more (395): Keto 10X some eggs and cheese by matelda12 on askubuntu.com
@Makyen That pattern looks like it's already caught by Pattern-matching website in body and Pattern-matching website in answer; append -force if you really want to do that.
@Makyen That pattern looks like it's already caught by Potentially bad keyword in body, Potentially bad keyword in answer, Pattern-matching website in body, and Pattern-matching website in answer; append -force if you really want to do that.
@Makyen That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
@Makyen That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
[ SmokeDetector | MS ] Bad keyword in answer, potentially bad ns for domain in answer, potentially bad keyword in answer (88): What is Fildena 100? by Fildena100 on stackoverflow.com
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, link at end of body, pattern-matching product name in body, pattern-matching website in body, +3 more (493): Infinity Boost review by ndsayarrier on askubuntu.com
@NisseEngström Yeah, a bit. Unfortunately, the symptoms make it appear to do with the database connection, which is something only Undo can fix (e.g. reboot the database server).
@Makyen That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
@Makyen That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
@Makyen That pattern looks like it's already caught by Potentially bad keyword in body, Bad keyword in answer, Bad keyword in body, and Potentially bad keyword in answer; append -force if you really want to do that.
[ SmokeDetector | MS ] Bad keyword in link text in body, bad pattern in url body, blacklisted website in body, link following arrow in body, pattern-matching website in body, +2 more (457): How to setup ATT Email on outlook by maytegarcia on dba.SE
[ SmokeDetector | MS ] Bad keyword in answer, blacklisted website in answer, potentially bad ns for domain in answer, potentially bad keyword in answer (180): One-way Trapdoor Function by deckardshaw on cs.SE
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, potentially bad ns for domain in body, potentially bad keyword in body (197): Truncated core dump error by Aegisvit64 on askubuntu.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in username, link at end of body, link following arrow in body, potentially bad ns for domain in body, +3 more (487): Acting as Fat Blocker by ketobodytone3 on meta.SE
[ SmokeDetector | MS ] Blacklisted website in body, body starts with title and ends in url, link at end of body, pattern-matching product name in body, pattern-matching website in body, +3 more (495): Rejuve Allure Cream However by rroknenamax on askubuntu.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, pattern-matching product name in body, potentially bad keyword in body, potentially bad keyword in title (295): Spring Hall Health Keto! by porylory on drupal.SE
[ SmokeDetector | MS ] Blacklisted website in body, potentially bad asn for hostname in body, potentially bad ip for hostname in body, potentially bad keyword in body (102): Recover lost 7z file by izabela anna on superuser.com
[ SmokeDetector | MS ] Potentially bad asn for hostname in body, potentially bad ip for hostname in body, potentially bad keyword in body (3): how to unlock 7z file? by izabela anna on askubuntu.com
I think I can fix this, but it might take me a bit. Redis logging is fine, but the main redis instance (for websockets n stuff) is very unhappy (actually the logging one might be too, I haven't checked yet).
@thesecretmaster Yeah, that's concerning. Was it just that executable, or other files associated with the Redis install/version too? Were there any other non-Redis executables affected (e.g. might the machine be compromised)?
As far as I can tell just the redis-server executable
I'd be much more likely to blame apt being weird rather than say it's compromised because just switching redis versions is a... weird thing to do if you've compromised the machine. And it switched back to system redis, which doesn't seem sketchy. And there's not much evil that can be done just with the redis box, besides change the appearance of some feedbacks.
@SmokeDetector The other two posts by this user on SO are plagiarized (I've flagged). Their post on SF is plagiarized (flagged). I've only checked one on SU, but that was also plagiarized (flagged). I have not checked their other posts on SU.
@EJoshuaS No. It if we see it in an SD report, it gets a tpu response, but it's not something we're looking for. Thus, it should not be manually reported.
@SmokeDetector This was edited during the grace period to something other than just a complaint. It's possible it had formatting problems resulting in the initial Markdown converting to HTML with just the complaint. It was further edited to be just a link to another SO Q&A. The version of this post which was initially reported (i.e. prior to the grace period edit), is arguably TP. It's something I think would be reasonable to block at the system level, but it's not a nearly as clear as most R/A.
