𝙽𝙴𝚃𝚁𝙴𝚂𝙴𝙲Why does CloudFlare insist on forwarding abuse reports to hosting providers and website owners? This makes no sense if the website operators and possibly also hosting providers are the criminals you're trying to stop!
kolya@kolya Yes, email would be much better. The problem is knowing WHERE to email an abuse complaint to CloudFlare unless you actually know someone who works at Cloudflare's security team.
Kevin Karhan 
@netresec @kolya that is intentinal because #CloudFlare is a #RogueISP.
- Just like #NameCheap and #GoDaddy they ignore messages sent to their abuse contacts.
Maybe send a #fax to their Munich Office from an Internet Cafe?
Kevin Karhan :verified: (@kkarhan@infosec.space)
@netresec@infosec.exchange because #CloudFlare is a #RogueISP who routinely hosts and supports #Cybercrime and #Terrorism actors, including #Deash and #KiwiFarms for the latter. - #Doxxing reports *and* refusing to acknowledge that they can in fact *yeet clients* off their network is their routine #ModiOperandi. Only once clients threatened to fire #ClownFlare did they fire KiwiFarms! https://en.wikipedia.org/wiki/Cloudflare#Kiwi_Farms
@netresec you're not supposed to send abuse reports to Cloudflare the same way you wouldn't send reports to an email server that an abusive email passed through on its way to you. Cloudflare consider themselves part of internet infrastructure in that way, not content providers. but this all well known.
of course you're free to question Cloudflare's status as infrastructure providers. just know that this debate has already been going on for a few years.
of course you're free to question Cloudflare's status as infrastructure providers. just know that this debate has already been going on for a few years.
@kolya Then let's keep the debate going! Giving up just because nothing has changed doesn't help.
@netresec I'm not even sure what your point is: Should infrastructure providers be made liable for abuse in your opinion? (VPNs too?) Do you question Cloudflare's status as a provider?
@kolya The main issue isn't about liability, but rather about unwillingness to take action against malicious actors using their services for illegal activities. Also, Cloudflare is much more than just a transit provider. They also run nameservers for entire botnets and C2 infrastructures.
https://infosec.exchange/@netresec/114743583440776224
https://infosec.exchange/@netresec/114743583440776224
𝙽𝙴𝚃𝚁𝙴𝚂𝙴𝙲 (@netresec@infosec.exchange)
@daniel@federation.network But Cloudflare do run the nameservers for many malware/botnet domains. They also forward TCP traffic to command-and-control servers from infected computers. So it's not so much about the hosted content, but rather the service they provide.
@netresec if they're not liable, why would they wade into this, muddy their neutral stance, invest into checks and personnel, only to open themselves up to lawsuits by customers?
all throughout this discussion you sound like an activist who has precious little knowledge about this topic, but strongly held opinions. kinda weird for a self-proclaimed network expert TBH.
all throughout this discussion you sound like an activist who has precious little knowledge about this topic, but strongly held opinions. kinda weird for a self-proclaimed network expert TBH.