W32.Sobig.E@mm question

K

Kev

I was using Outlook Web Access into the firm's Exchange server across the
net and I got an e-mail from a colleague (who I don't think I know) saying
that an e-mail from me - apparently sent by me this afternoon - had the
W32.Sobig.E@mm virus infected attachment.

I've scanned my machine (XP Pro) and don't see any sign of it - quick look
in the registry and in the processes showed nothing. I've run the McAfee
Stinger utility and found nothing with that either.

I don't double click on attachments, even from trusted people, before
scanning them and my machine always has the latest version on McAfee
running.

What's going on ?

Many thanks
 
L

Lyle H. Gray

Kev said:
I was using Outlook Web Access into the firm's Exchange server across
the net and I got an e-mail from a colleague (who I don't think I
know) saying that an e-mail from me - apparently sent by me this
afternoon - had the W32.Sobig.E@mm virus infected attachment.

I've scanned my machine (XP Pro) and don't see any sign of it - quick
look in the registry and in the processes showed nothing. I've run
the McAfee Stinger utility and found nothing with that either.

I don't double click on attachments, even from trusted people, before
scanning them and my machine always has the latest version on McAfee
running.

It is in the design of W32.Sobig.E@mm that both the TO: address _and the
FROM:_ address are taken out of an infected computer's address book.
Basically, someone who has both your email address and your colleague's
email address has the virus infecting their computer. You would need to
look at the full headers for the infected email to have some idea where
the message actually came from.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

How does Sobig.E infect? 4
W32.Netsky@mm 4
W32/Mytob Virus 9
W32/Bagz.f@MM 2
w32/Netsky.b@MM 1
W32.Swenn.A@mm 35
Probably a W32.Bugbear.B@mm Infection? 1
W32.RontokBro.B@mm 4

Top