UPDATE
I've been hacked again. I've spent a long while trying to work out how they did it. They reset my second Netgear Nighthawk router which I have working in AP mode.
It recorded the MAC Addresses of the hacker and they used a Sky router to hack mine. I'm thinking this might be a neighbour doing this.
The only possible way into my router that I can see is by using the Wi-Fi Protected Setup (WPS) pin code they previously used. I admit I used to have this second router open using the main router to block any new connections. But as they didn't get access to my main router, they did have the WPS pin from the method they used to hack the WPS first time round.
I updated the firmware and locked the router down to also block any new connections. The WPS pin code option was already disabled, but if they managed to bypass it last time, what I didn't think about was that the router remembers a WPS pin code so a user doesn't have to enter it each time they connect.
Since I have never used the WPS pin code method to connect any device to my router, I really don't want any pins to be remembered by the router.
So, by unticking these boxes (see image), it tells the router not to remember any WPS PIN codes.
If you try this, any device that connected to your router by using the PIN Code will not be able to automatically connect. This does not affect manual connections using the SSID anf password method.
To be frank, the WPS is often used by owners who don't understand much about router security and in itself, is a security risk. The annoying thing, although you disable the pin option, the physical button to enable WPS on the router still works and can't be disabled. The router also generates new PIN Codes if the tick box is unticked but it doesn't use them. It would be better/safer if Netgear (and other manufacturers) disabled the entire WPS feature.
For your own security, at least, disable the WPS option on any make of router to remain safe. Untick the Enable Routers PIN (or tick it if it says Disable Routers PIN on your router).
Screenshot 2022-06-25 143512.png
Anyway, the router is back up and running again. Lets see how long it takes the toerags to find another loophole.
https://kb.netgear.com/19824/How-does-m ... ce-attacks
Also see:
https://kb.netgear.com/24103/How-do-I-s ... awk-router
You do not have the required permissions to view the files attached to this post.