Um chill out. It could have been some weird IP spoofing attack where the host gets confused and thinks a remote connection is actually localhost and grants it

Um chill out. It could have been some weird IP spoofing attack where the host gets confused and thinks a remote connection is actually localhost and grants it some privilege or other. For example maybe you have a ton of services setup to only listen on localhost:port. Maybe there's some exploit that allows connections from outside. That's what the title sounds like to me, which is quite different. anyway.