> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Title - Position 0-17: sarkariduniya.com Body - Position 0-17: sarkariduniya.com Username - Position 0-17: sarkariduniya.com
> Potentially bad ns for domain in body, potentially bad ns for domain in title ---------- Title - componentpro.com NS suspicious ns4.a2hosting.com.,ns2.a2hosting.com.,ns3.a2hosting.com.,ns1.a2hosting.com. Body - componentpro.com NS suspicious ns4.a2hosting.com.,ns2.a2hosting.com.,ns3.a2hosting.com.,ns1.a2hosting.com.
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Title - Position 0-14: virtatrade.com Body - Position 0-14: virtatrade.com Username - Position 0-14: virtatrade.com
> Pattern-matching website in body, pattern-matching website in title ---------- Title - Position 4-18: supplement.com Body - Position 4-18: supplement.com
@TetsuyaYamamoto 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.
> Pattern-matching website in body, pattern-matching website in title, potentially bad ns for domain in body, potentially bad ns for domain in title ---------- Title - Position 4-18: burn1250try.co Title - ketoburn1250try.com NS suspicious dns1.namecheaphosting.com.,dns2.namecheaphosting.com. Body - Position 4-18: burn1250try.co Body - ketoburn1250try.com NS suspicious dns1.namecheaphosting.com.,dns2.namecheaphosting.com.
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Title - Position 0-15: logodesigner.ae Body - Position 0-15: logodesigner.ae Username - Position 0-15: logodesigner.ae
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Title - Position 0-19: ozcandegirmenci.com Body - Position 0-19: ozcandegirmenci.com Username - Position 0-19: ozcandegirmenci.com
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Title - Position 0-14: web3mantra.com Body - Position 0-14: web3mantra.com Username - Position 0-14: web3mantra.com
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Title - Position 0-12: meramaal.com Body - Position 0-12: meramaal.com Username - Position 0-12: meramaal.com
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Title - Position 0-14: ph375guide.com Body - Position 0-14: ph375guide.com Username - Position 0-14: ph375guide.com
> Pattern-matching website in body, pattern-matching website in title ---------- Title - Position 0-19: healthadvisor365.co Body - Position 0-19: healthadvisor365.co
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username, potentially problematic ns configuration in body, potentially problematic ns configuration in title ---------- Title - Position 0-20: laravelecommerce.com Title - Suspicious nameservers: all IP addresses for laravelecommerce.com are in set {'162.144.202.188'} Body - Position 0-20: laravelecommerce.com Body - Suspicious nameservers: all IP addresses for laravelecommerce.com are in set {'162.144.202.188'}
> Pattern-matching product name in body, pattern-matching product name in title, pattern-matching website in body, pattern-matching website in title, pattern-matching website in username, potentially bad asn for hostname in body, potentially bad asn for hostname in title ---------- Title - Pattern-matching product name: Position 0-14: healthketodiet Title - healthketodiet.com address 185.224.137.142 in ASN 47583 Title - Position 10-18: diet.com Body - Pattern-matching product name: Position 0-14: healthketodiet
@TetsuyaYamamoto That pattern looks like it's already caught by Pattern-matching website in answer, Potentially bad keyword in answer, Pattern-matching website in body, and Potentially bad keyword in body; append -force if you really want to do that.
@TetsuyaYamamoto That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; append -force if you really want to do that.
@TetsuyaYamamoto That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; append -force if you really want to do that.
> Potentially problematic ns configuration in body, potentially problematic ns configuration in title ---------- Title - Suspicious nameservers: all IP addresses for learnthenew.com are in set {'103.53.43.60'} Body - Suspicious nameservers: all IP addresses for learnthenew.com are in set {'103.53.43.60'}
@TetsuyaYamamoto That pattern looks like it's already caught by Potentially problematic ns configuration in answer and Potentially problematic ns configuration in body; append -force if you really want to do that.
[ SmokeDetector | MS ] Url-only title, blacklisted website in body, blacklisted website in title, body starts with title and ends in url, link at end of body, +8 more (895): evaherbalist.com/green-force-keto/ by Pmwprvbf on askubuntu.com
@tripleee 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.
@tripleee 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 ] Url in title, bad keyword in body, blacklisted website in body, blacklisted website in title, body starts with title and ends in url, +9 more (989): evaherbalist.com/green-force-keto/ by Friltdpt on drupal.SE
@iBug 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.
@iBug That pattern looks like it's already caught by Offensive body detected, Toxic body detected, Offensive answer detected, and Toxic answer detected; append -force if you really want to do that.
Background
I am developing a tool designed to help programmers use a popular data-manipulation library. This tool asks the user for input-output examples and an English description or list of keywords describing the desired manipulation. Then, the tool will search for a program using the library...
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, pattern-matching product name in body, potentially bad keyword in title (295): vital-keto-avis/ by awldaazaad on apple.SE
@TetsuyaYamamoto That pattern looks like it's already caught by Potentially bad keyword in body, Potentially problematic ns configuration in answer, Potentially problematic ns configuration in body, and Potentially bad keyword in answer; append -force if you really want to do that.
@TetsuyaYamamoto That pattern looks like it's already caught by Potentially problematic ns configuration in answer and Potentially problematic ns configuration in body; append -force if you really want to do that.
> Blacklisted website in body, blacklisted website in title, potentially problematic ns configuration in body, potentially problematic ns configuration in title ---------- Title - Position 0-13: zoomadmin.com Title - Suspicious nameservers: all IP addresses for zoomadmin.com are in set {'209.105.233.229'} Body - Position 0-13: zoomadmin.com Body - Suspicious nameservers: all IP addresses for zoomadmin.com are in set {'209.105.233.229'}
[ SmokeDetector | MS ] Blacklisted website in answer, pattern-matching website in answer, potentially bad asn for hostname in answer, potentially bad ns for domain in answer (174): Creating fillable PDFs by Mellisa Garcia on tex.SE
tpu- feedback received
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, body starts with title and ends in url, link at end of body, +7 more (888): Keto Tone Diet Pills Reviews by dixiebensoniy on askubuntu.com
[ 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 (495): Supportive in losing fat effortless by helenstines on askubuntu.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching product name in body, pattern-matching product name in title, +4 more (594): Keto Weight Loss Plus France by awldaazaas on apple.SE
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, body starts with title and ends in url, pattern-matching product name in body, pattern-matching product name in title, +2 more (493): Keto Weight Loss Plus Avis by EllenaFoy on wordpress.SE
@angussidney @ThomasWard @NobodyNada @Henders @iBug It looks like MS going down has managed to cause SD to become non-responsive and none of the instances to come out of standby. For the first one of you that gets in, could you kick your instance(s) so we have an SD instance running. The rest of you may need to also kick your instances to get them running in standby (status unknown, although all were pinging MS just fine prior to it going down). Thanks.
