F
frank
A few weeks ago I got hit with the 'smithfraud' spyware.
I did a system restore to bring things back, downloaded
the MS beta antispyware, ran it to clean up left over
remnants of the spyware and turned on the MS antisypware
realtime monitors.
I've been downloading antisypware updates regularly (at
least once a week) and got the latest and greatest
definitions on June 10.
But, yesterday, I got hit with smithfraud again (or at
least that's what the error screen was saying. Plus, the
file wp.bmp was left around after I cleaned up and that's
supposedly a smithfraud signature.)
So, it seems like the beta didn't detect the intrusion of
the sypware because the beta was running its monitors and
I had updated signatures.
This isn't a complaint, just an observation. I'm still
on XP SP1.
I did a system restore to bring things back, downloaded
the MS beta antispyware, ran it to clean up left over
remnants of the spyware and turned on the MS antisypware
realtime monitors.
I've been downloading antisypware updates regularly (at
least once a week) and got the latest and greatest
definitions on June 10.
But, yesterday, I got hit with smithfraud again (or at
least that's what the error screen was saying. Plus, the
file wp.bmp was left around after I cleaned up and that's
supposedly a smithfraud signature.)
So, it seems like the beta didn't detect the intrusion of
the sypware because the beta was running its monitors and
I had updated signatures.
This isn't a complaint, just an observation. I'm still
on XP SP1.