MysteryFCM

Moderators
  • Content count

    6,681
  • Joined

  • Last visited

About MysteryFCM

  • Rank
    Forum Deity

Contact Methods

  • Website URL
    http://it-mate.co.uk

Profile Information

  • Location
    Tyneside, UK

Recent Profile Visitors

61,247 profile views
  1. It was blocked due to abuse of our affiliate program, following the spamming of a bogus Malwarebytes FB page (hxxps://www.facebook.com/mawarebytescouponcode/ which led to hxxp://www.thesoftwareclub.com/malwarebytesfb.html). As I've seen nothing recent, the block will be removed on the next update.
  2. You've still got malicious files present. e.g.; hxxp://u.teknik.io/mYO8X.exe
  3. Please contact legal@malwarebytes.com
  4. The block is being removed. The cause of the listing was a phish found at; hxxps://form.jotformeu.com/71105759469364
  5. There's still malware on the site. hxxps://u.teknik.io/xAIH9.exe
  6. Confirmed F/P. Block is being removed.
  7. Moved from Website Protection F/P reports to a more appropriate forum.
  8. The site may be clean, but these chaps aren't blacklisted for malware etc, they're listed because they've been spamming the likes of guestbooks, forums, Facebook etc for years.
  9. We're not blocking that IP. Please post the domain to which you are referring.
  10. The block will be removed on the next update.
  11. This is a false positive and will be unblocked on the next update.
  12. I've gone through the hostname and IP history and strongly recommend checking the software involved isn't routing the request elsewhere as the NTP server specified (nor indeed, any other NTP server), has never been associated with or resolved to, 104.236.116.147
  13. The site has been re-checked and will be unblocked on the next update.
  14. The cause of this is emails embedding the domain (guessing you use HTML email instead of plain text (strongly recommend changing that)) in the content. The block itself is on the gTLD (.bid) and is caused by heavy abuse of it for malicious purposes. Until this changes, you can add an exclusion for the domain itself if you wish (Settings -> Exclusions)
  15. The block was put in place because TP-Link lost control of the domain (amongst others) last year; http://www.computerworld.com/article/3090959/networking/tp-link-lost-control-of-two-domains-used-to-configure-routers-and-wi-fi-extenders.html