Jump to content

api.skritter.com (206.189.217.142) blocked for phishing


prokopcm

Recommended Posts

Hi, a user reported (and I have confirmed with my own installation of Malwarebytes on another computer) that certain routes on our API are blocked for phishing. Specifically, only requests to our v2 API are blocked (https://api.skritter.com/v2). Routes to our v1 or v3 APIs have no issue, even with Malwarebytes enabled. This blockage causes the main functionality of our service to fail to load when a user has Malwarebytes enabled.

We are not doing any phishing and, as far as we can tell, there have been no incidents or any other reasons to suspect our domain had been compromised. All sites I've tried to run our IP through come back clean (e.g. https://www.virustotal.com/gui/ip-address/206.189.217.142/detection). Can our API be unflagged from your database? Is there anything we can do on our end to avoid triggering your antivirus? Happy to provide more information/details if needed. Thanks.

skritter_phishing_log.txt 6239c330-ea03-11ea-a394-7085c2a63f6c.json.txt

Link to post
Share on other sites

  • Staff
13 minutes ago, prokopcm said:

Hi, a user reported (and I have confirmed with my own installation of Malwarebytes on another computer) that certain routes on our API are blocked for phishing. Specifically, only requests to our v2 API are blocked (https://api.skritter.com/v2). Routes to our v1 or v3 APIs have no issue, even with Malwarebytes enabled. This blockage causes the main functionality of our service to fail to load when a user has Malwarebytes enabled.

We are not doing any phishing and, as far as we can tell, there have been no incidents or any other reasons to suspect our domain had been compromised. All sites I've tried to run our IP through come back clean (e.g. https://www.virustotal.com/gui/ip-address/206.189.217.142/detection). Can our API be unflagged from your database? Is there anything we can do on our end to avoid triggering your antivirus? Happy to provide more information/details if needed. Thanks.

skritter_phishing_log.txt 739 B · 0 downloads 6239c330-ea03-11ea-a394-7085c2a63f6c.json.txt 2.12 kB · 0 downloads

Hello, thanks for bringing this to our attention. We've reviewed the site again and have determined it no longer warrants being blocked so we've removed it from our database. 

Removal should be reflected in the next database update going out in a few hours or so.

Link to post
Share on other sites

  • TeMerc locked this topic
Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.