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.

  • SayCyberOnceMore@feddit.uk
    link
    fedilink
    English
    arrow-up
    2
    ·
    12 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
      ·
      12 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
        2
        ·
        9 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.

        • SayCyberOnceMore@feddit.uk
          link
          fedilink
          English
          arrow-up
          1
          ·
          5 hours ago

          I agree this is an old thing, my firewall has blocklists and allowlists to prevent known bad IPs and allow only the countries I travel to.

          But if Nabu Casa is an outbound VPN, then my blocks won’t work. I’d need them to block

          Either way it would make sense for HA to also use some crowdsourced blocklists as a 2nd level defense