Since the KlezG worm spoofs the originators email address, is there any way to find out which pc on a network is infected without scanning every pc for the virus?
You can almost to do a trace by checking the message header. Even though Klez spoofs the sender address, the mail header will still contain the originator.
Also, having a mailserver-based AV program will help inform you who the actual sender was.
I have a question on how to check the header. We are still plagued by the Klez virus, and have been unable to track down the infected machine (nearly 1000 machines to check). We are also running Trend Micro's Interscan Viruswall on an SMTP server. How do I go about viewing the email headers to find out the originator of the email as opposed to the sender?? Thank you in advance for any information.
Depends on which email system you're using. In Exchange/Outlook combo, you can open the email (don't run the attachment ), and look at View/Options and see the Internet Headers information. In Yahoo Mail, you can just expand the headers.
Did you get anywhere with this? I didn't. I downloaded something called emailtrackerpro which was supposed to track back. Load of nonsense. It told me the originator was in Sweden, and told me where Sweden is. Terrific. Peter Meachem
peter@accuflight.com
This didn't quite work for me. We run Trend Micro's Interscan Viruswall, which basically allows us to forward all outgoing mail thru it to be scanned, and any incoming mail goes thru it to be scanned also. We're running Exchg5.5, with a mixture of Outlook and Outlook Express clients. When I look at the options on the emails all I'm seeing is either the Interscan server as the "From" or the machine that the user read the email. I've checked all of these machines and it appears as though they do not have the virus. Norton Corporate Edition is running on the workstations.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.