Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

files.slack.com #1518

Closed
alfaridi opened this issue Feb 1, 2021 · 5 comments
Closed

files.slack.com #1518

alfaridi opened this issue Feb 1, 2021 · 5 comments

Comments

@alfaridi
Copy link

alfaridi commented Feb 1, 2021

Is there any valid reason to include files.slack.com?

@welcome
Copy link

welcome bot commented Feb 1, 2021

Hello! Thank you for opening your first issue in this repo. It’s people like you who make these host files better!

@shreyasminocha
Copy link
Contributor

It's from Threat-Intel. @davidonzo

@alfaridi
Copy link
Author

alfaridi commented Feb 1, 2021

Uhm, but I believe Slack is widely used by many companies. The files.slack.com is a file repository.

@PeterDaveHello
Copy link

PeterDaveHello commented Feb 1, 2021

I also noticed this issue yesterday, as @shreyasminocha says, it's from Threat-Intel, and Threat-Intel is also referenced by another few lists, e.g. EnergizedProtection, so if you are using multiple block lists(I know many users are), the domain might also be blocked by some other block lists.

Issue davidonzo/Threat-Intel#16 was opened earlier, feel free to leave comment if you found something important or helpful :)

@davidonzo
Copy link

Fixed, see the conversation on twitter: https://twitter.com/AdamSurak/status/1356152687289655297
The domain has been whitelisted, as ever in these cases. Of course, be carefull, since the downloaded file from the host is an effective malware.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants