Freshly created host and already hundreds of access attempts (failed, so far)

Hi,

Today I tried to deploy my first Firebase app, it still fails, so I’ll work on that.
Meanwhile, I suppose the Cloud Host has been created and currently empty (only a message saying “Backend Not Found” which will probably change once I’m able to deploy).

My issue is anyway related to what I’ve seen in the Log after few hours. Log was already full of failed attempts on that specific hostname trying open the most various pages (/shop /account /login /carrillo /dashboard etc) , probably to check if there is something open and ready to hack. They currently fail with 404 or 301.

I’m currently a bit worried of that. First time I try to deploy something on web , thrilled by the easyness of using Firebase, maybe it’s normal and that’s just a warm Welcome from the hacker community.

Did anyone noticed anything similar? What’s your view or approach with that?
Is there anything that can be done to keep them out? (like firewall, IP filtering, turning off server when I don’t need it)
Nevertheless, I also wonder if that traffic will be accounted into my invoice…

R

1 Like

I’m hacked they blocking me

I had the same issue and concern. I then signed up for a free cloudflare account and set up some security rules. I don’t have any of those accesses anymore. Cloudflare blocks all of them.

Thank you Joe, this is a very useful information. I’ll check that out for sure.

I’m still fighting with build+deploy with Google Cloud. It looks like that when some “secrets” (like Firebase Admin SDK keys) are involved it gets complicated.