P
Peter Nolan
Hi,
I am using outlook xp on win xp dell laptop...
When I sent emails out I am occasionally seeing 'sending 0 of n'
emails.
This usually only occurs when sending acknowledgements for emails and
in these cases there are no acknowledgments......
I scanned using McAffee and AdAware and it showed up a keylogger
installed onto the OS disk which I have rebuilt inside the last 40
days.........I deleted the key-logger but it was in the temp folder
for my user name on the laptop.
So I think what has happened is that I have been 'bugged' by a key-
logger that was most likley delivered by email but did not get
detected by mcafee as the email was opened and it has been sending
keystrokes to whoever bugged me......(hope they have better things to
do than read my typing)......
Has anyone seen such a delivery mechanism for bugging? If so, how
would I make sure that the bug is not in any of the emails I am
opening so that I do not re-infect myself..?
Or is there any way to check outlook to see where the bug might be
being invoked?
Thanks
Peter
I am using outlook xp on win xp dell laptop...
When I sent emails out I am occasionally seeing 'sending 0 of n'
emails.
This usually only occurs when sending acknowledgements for emails and
in these cases there are no acknowledgments......
I scanned using McAffee and AdAware and it showed up a keylogger
installed onto the OS disk which I have rebuilt inside the last 40
days.........I deleted the key-logger but it was in the temp folder
for my user name on the laptop.
So I think what has happened is that I have been 'bugged' by a key-
logger that was most likley delivered by email but did not get
detected by mcafee as the email was opened and it has been sending
keystrokes to whoever bugged me......(hope they have better things to
do than read my typing)......
Has anyone seen such a delivery mechanism for bugging? If so, how
would I make sure that the bug is not in any of the emails I am
opening so that I do not re-infect myself..?
Or is there any way to check outlook to see where the bug might be
being invoked?
Thanks
Peter