Ok Ive been checking my firewall logs and found a date coloration between a suspect face book account.
On the same day that i received a message via facebook then checked the profile of the account holder I had a stack of hits on my avast firewall.
Now i'm not sure that the two are related but thought it worth checking out.
As a precaution I've ran Avast boot time scan and full Avast scan and a Malware bytes full scan and they have found nothing dumped on my machine.
Of note i was having issues with Chrome last month and it seems to have logged lots of events related to Chrome.exe perhaps a conflict between a chrome update and Avast?
What do you mean by a "stack of hits on my avast firewall"? Do you mean that the log shows that it blocked a bunch of stuff?
If so, then likely there is not much to worry about...that is what firewalls are there for...to block stuff.
As to the timing, it is likely a coincidence.
First, to my knowledge, you cannot determine things like IP address, etc from someone who connects to a Facebook profile unless the Facebook profile page is completely false (i.e. it is not even a real Facebook page). In other words, Facebook is locked down enough when you are actually on a Facebook page (even if the Facebook profile is a fake one meant for less than honorable purposes) that there is not much you can directly do while actually in the Facebook system. To my knowledge, it is more the external links on Facebook posts/pages that create the most security type problems. I believe the closest you can get to threats directly third party Facebook Apps, but even then it is mostly potential privacy threats (i.e. Apps can get access to your posts and lists of Friends, etc). If all you did was look at a profile on Facebook, then I don't believe that can directly lead to targeted attacks at your computer due to that...but I could be wrong.
Second, firewalls (whether software or hardware) typically only block stuff that from sites that you did not initiate. If you initiate the contact (as you effectively did here), then the firewall will typically not block it. The big exception to this are firewalls that a designed to have to "learn" your behavior. In the case of these types of firewalls (and depending on their settings), they might at first block something you do and then toss up a dialog box essentially asking "did you want [such and such program] to be allowed to have an outbound connection". If you say yes, then the firewall will remember that program is allowed to have those kinds of outbound connections for both manual stuff as well as automatic stuff. If you say no, then that program will be blocked. So, when you install such a firewall, when you use your browser for the first time after installing the firewall, it will ask if you want to allow the browser to have a connection. Once you do, then that firewall will no longer block connections from the browser unless it is smart enough to check different types of internet traffic from browsers (most browser traffic will be http stuff, but you can also do things like ftp from many browsers as an example). This is at least the basics. There might be some types of traffic that could be blocked by a firewall even though you effectively initiated the connection, but I am not knowledgeable about firewalls to know for sure.
At the end of the day, if you are concerned, then you have started with the correct things to do...scan you computer with your antivirus program (Avast in this case) and also Malwarebytes Antimalware. You can then check your ports vulnerabilities with GRC as suggested by Wolverine 7
. If you do and you are "behind" a router (i.e. you have some sort of internet router either from your ISP or your own, which is the case with the just about everyone with an internet connection) as well as your software firewall, then you should get a "stealth" result (just about any router should stealth all your inbound ports and then software firewalls are for if you don't have a router, are using the computer on a public network, or for some help with outbound protection). Last, if you are still concerned, then you might want to post to the "Am I Infected?" forum.