I pay for the Nabu Casa subscription for remote access to Home Assistant. Mostly as a way to give them money for a great service, but it’s convenient and felt pretty secure. It should be the only remote way into Home Assistant. About an hour ago I got a login attempt notice that an IP was trying to access API/config. The IP is in some bad IP databases. What I found interesting was that the log shows an AI bot. A Google Gemini bot specifically. Makes me worry that AI is going to make yet another aspect of life frustrating and unfun.

  • frongt@lemmy.zip
    link
    fedilink
    English
    arrow-up
    16
    ·
    7 hours ago

    Welcome to the Internet. If it’s exposed, people and bots are going to be banging on it.

  • 4am@lemmy.zip
    link
    fedilink
    English
    arrow-up
    1
    ·
    4 hours ago

    I’ve got Nabu Casa and IPs from the “googleusercontent.com” domain have been hitting my instance about once per day for the last week or so.

    Use strong passwords and let’s hope that the login page doesn’t have any vulnerabilities…

    • InEnduringGrowStrong@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      2
      ·
      2 hours ago

      and let’s hope that the login page doesn’t have any vulnerabilities…

      Home assistant also supports mTLS.
      home assistant is something you’d likely ever want to allow from a handful of trusted devices, so deploying a client certificate on them can make sense.
      This way a non-onboarded device doesn’t even get to the html part, it’s denied upstream by a reverse proxy before HA is involved.

      • captcha_incorrect@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        8 minutes ago

        I follow a guide for authelia and caddy, making it so that I can put authelia infront of anything without it the service behind supporting it. Still have to authenticate on the service behind but that is a small inconvenience.

  • Ebby@lemmy.ssba.com
    link
    fedilink
    English
    arrow-up
    11
    ·
    9 hours ago

    I get frequent login attempts from Google servers too. I got the impression they offer a SaaS service some script kiddie uses to attack home assistant installations.

    Make sure passwords are unique and activate incorrect login bans.

  • Godnroc@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    ·
    8 hours ago

    104.28.222.47? That one showed up in a log yesterday for me. Super glad the latest update added the option to see the IP for login attempts.

    • gdog05@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      3
      ·
      7 hours ago

      This one was 66.187.5.19. I tried to find a way to report their behavior on hostodo (the service they’re using) but they don’t seem to have a report option. I’m guessing because they don’t want to prevent this kind of thing.

  • SayCyberOnceMore@feddit.uk
    link
    fedilink
    English
    arrow-up
    2
    ·
    7 hours ago

    I’ve not looked into Nabu Casa much, is it an outbound VPN from our HA instances to their servers? If so, maybe the Nabu Casa admins need a blocklist?

    • gdog05@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      1
      ·
      6 hours ago

      That is exactly it, yes. And I am thinking about reaching out to them about it and their blocklist. But after thinking about it, anyone with $16 in hosting can start an AI hacking instance. It’s just going to get worse.

      • i_am_not_a_robot@discuss.tchncs.de
        link
        fedilink
        English
        arrow-up
        1
        ·
        4 hours ago

        This kind of thing has been going on since long before “AI.” Expect anything connected to the internet will have failed login requests. That’s why there is a login system.