Hi @techresearch7777777 ,
It is possible that there was a lingering session in the background that was causing the connection attempts to persist even after you had closed SSMS on your machine. This could be due to a number of factors such as an unstable network connection or a poorly coded application.
Another possibility is that your machine had been compromised and a third-party application was attempting to connect to the SQL Server using your login credentials. In this case, changing your login password would have terminated the unauthorized connection attempts.
Regardless of the cause, changing your login password was a good precautionary measure to take in order to prevent any further unauthorized access attempts.
Because it is not known what kind of monitoring tool you are using. You can use the Extended Events that come with SQL Server. It can capture specific events.
Right-click on "Extended Events" and select "New Session Wizard".
In the "New Session Wizard" dialog box, specify a name for the session, and select "Start immediately".
You can choose more fields according to your needs.
Please refer this article for more details: https://www.sqlshack.com/creating-a-sql-server-audit-using-sql-server-extended-events-and-triggers/
Best regards,
Seeya
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".