Your email address probably turned up in a leaked password database. Most people re-use passwords across services, so trying those leaked credentials across loads of other services represents low-hanging fruit.

You've got nothing to worry about if you used a unique password and you turned on 2FA.

>>28117

https://haveibeenpwned.com/

I sort of solved the issue by making an alternative email address not linked to anything, and linking it to my Microsoft account. You can then choose which aliases are able to log into your account. So if you're getting all this shit on your JohnSmith@gmail.com Microsoft account, you can make a RickWaller@gmail.com account, and make it the only way of accessing the Microsoft account. Then if they try and log in the JohnSmith account it will say there is no account in that name. But you will still receive updates to the JohnSmith account, it just needs RickWaller to get in.

I feel like I explained this incredibly badly.

>>28119
There was no issue to solve.

Sort of not really related but also not unrelated, a few years ago I looked at the logs on my wi-fi router, and I noticed that somebody had tried to connect to it almost 50 times over one evening. The date sort of matched the week when a couple moved into the flat downstairs, so my guess was that they had no Internet connection yet and just randomly tried to hack into whatever wi-fi networks were available. The computer name with which they tried to connect to my wi-fi was nondescript enough to not give me any kind of leads. Whoever did it then gave up after that evening and apparently never tried again.

Is there a way you can give somebody a crippling computer virus if they successfully break into your wi-fi network?

>>28121
You'd need to know if they were connecting illegitimately or if it was just you with your phone or whatever. You can have access control lists, and MAC address filtering, and tricks like that, but then you might as well just not let whoever's not on the list connect in the first place. There are honeytrap servers, where some networks have a server that's really easy to connect to but doesn't actually have what the hackers are looking for, but it'll probably be quite a ballache to set up a server to run 24/7, even virtualised, just in case someone hacks into your network.

>>28117
>>28118
Turns out it's been "pwned" since 2009, and numerous times since. Even, seemingly, to things I don't recall ever hanging over an email address too.

>>28119
I've got the same thing going on so I should be fine.