Norton aggressively blocking NWJS desktop build activity?

Hi, I primarily export html5 web games, but occasionally make desktop builds as a second option.

I was doing this with my most recent game tonight, and when I ran it to test it, it started fine, but Norton has been aggressively asking me to block "Suspicious network activity" pinging over and over and over, long after the game was closed. (Multiple pings for each second the game was open, based on the timestamps) It's still going right now in fact. (I eventually hit "block always" and there were about 3 pages of blocks logged)

Is there a particular reason that an NW.JS build would do this? My game uses local storage to save a little bit of continue data, but otherwise shouldn't be writing or accessing the network that I'm aware of.

This certainly makes me wary of distributing a desktop build. I don't recall any previous games I've built doing this, though it has been over a year since I've made a desktop option.

Context I forgot: I'm running C3 on Chrome on Windows 10, and I'm only attempting to build the Windows 32 and 64 versions, not worrying about Mac or Linux currently, as I don't have either platform.

I was thinking about it, and I decided to go back and run some old NWJS desktop builds that I made quite awhile ago. They are now having a similar issue, despite having been fine previously:

As for my new game, this is the popup that Norton sends:

I should note, the games aren't actually blocked... Norton just accuses them of this or that, but lets them run. I can just click "always allow" or "always block" and it'll solve the issue for that single game.

However, I've been toying with the idea of putting games on Steam, and this seems like a problem. Does anyone know what the root issue is? Is this just Norton being overly protective, or is there something I'm doing wrong when making the builds?