McAfee Worm Message

  • Thread starter Thread starter Robert Jones
  • Start date Start date
R

Robert Jones

This is so weird I still can't believe it really happened.

I wrote a Visual Basic (v6) app that referenced Outlook. All I wanted to do
was at the end of a routine was to import some data into a database and
email someone with the results of the import

Everything was working fine. What I usually do prior to deployment is change
the references so the outlook variables are "object" rather than
"outlook.application" and "outlook.mailitem" etc - this makes the
application more robust - it will support older versions of office etc.

However when I did this the other day McAfee jumpted up with a "unknown
worm" message and ran off with my executable (put it in the quarentine
folder).

By changing the references back to "Outlook.Application" instead of "Object"
everything works fine.

By changing the references from "Outlook" to Object I get the worm messages
again.

Any cunning plans? I really need to fix this!!
 
dump mcafee maybe. although it's best at detecting extended threats than
Norton, the second lets you work a lot more smoothly (no unexpected one or
two second halts and I bet no more dummy messages).
Besides it's not even consistrent. You can work around it's protection by
changing from object to Outlook.App.
Maybe you can write to mcafee and point this out as a savere bug (as it
is...). They will probably fix it sometime.
 
You can tell the McAfee script stopper to trust your code. Norton doesn't
allow that and in fact there are many more problems with code with Norton
than with McAfee.
 
Back
Top