The recent "Drupalgeddon" attack revolved around downloading scripts from multiple sites onto a server and then executing them.
It'd be great to block some requests before they even before the process of loading the pages. Particularly anything that blocks addresses containing strings defined by the user. Blocking addresses containing the phrases base64, github, pastebin, ghostbin, curl, wget and so on would all prevent future hack attacks.
However, these would need to be blocked long before ever becoming "page not found" errors.
Rather than develop it as a separate module, it'd be better to build that "ban before process" into this module. Would that be of interest to the maintainers?
Closed: works as designed
1.8
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.