CloudFlare IPs + Apache Logs Showing Criminal Hacking

A server that I manage had been receiving malicious files from a fake “” website, which has been successfully blocked from being accepted. However, what it disturbing is that I find in the access logs three IP addresses that are attempting to exploit the server that caused the malicious files to be uploaded in the first place … and all three (now four) belong to Cloudflare and they continue to attack the server!
How do I report someone hiding behind a Cloudflare IP address, when I don’t know who the real culprit is behind your IP addresses or have your Cloudflare servers been compromised? - Seattle, Washington, USA - London, England, UK - Frankfurt am Main, Hesse, Germany - Melbourne, Victoria, Australia

Cloudflare does not provide IP addresses to the masses to use them for outbound connections.

You can report abuse at any time here:

Are you suggesting that Cloudflare is behind it then? It’s their IP’s showing up in the access logs, if the IP’s weren’t theirs, I’d be taking my concerns elsewhere.

Second, the abuse form doesn’t take into consideration that only an IP is known and that the problem is with Cloudflare IP addresses showing up and doing questionable actions. IP addresses are refused by the form as “URLs” and the field is requiring it be filled out.


You can also send an email to abuse[@] with a detailed description and logfiles.

It’s also possible that the IPs are simply spoofed but that need’s to be checked by Cloudflare staff.

I assume that you’re not a Cloudflare user. Am I right?

Not exactly. I have an account, but no services attached to it. It wasn’t until today that I “created” the community account since the abuse form wasn’t helpful in reporting suspicious activity from Cloudflare IPs. I was hoping they could figure out what’s going on and why their IP shows up in the access logs showing their addresses sending suspicious POST data to Apache that directly resulted in Apache running malicious code that ended with the server downloading a Trojan through wget, then curl when wget was no longer accessible to the code.

That was my question. :slight_smile:

As mentioned in my last post. Use the old fashioned way: send an email to the abuse team.

They can. Send them your logs. If they can see any suspicious behavior originating from
their network they can take apropiate action.

Unfortunately abuse is something the community can’t really help with.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.