I originally posted this on an Outlook discussion group, but have since
realised Security might have been more appropriate, so am copying it here
with minor additions.

For less than one full day, both NAV and AVG indicated that files that are
constantly created in "C:/Documents and settings/<user>/Local
settings/Temp" with names "CC*.tmp" (they appear to be named using
hexadecimal notation of a byte) have the Netsky.P or .Q worms. Is this
NAV/NIS creating these files as a result of using MS Outlook, and why would
the files have an old worm?

Investigating how these worms work shows that the system does not appear
to be infected with these worms. But the "CC*.tmp" files are always being
recreated.

Any suggestions how to eliminate the problem?

For further information, warning messages from AVG and NAV only now appear
when I access that folder/files to try to solve the problem. Maybe there's no
real problem after all. But if NAV/NIS is creating those files, then why
would it be creating them with an apparent security flaw?

Kevin

RE: What creates these files? by MarcoSpoel

MarcoSpoel
Thu Sep 22 07:12:01 CDT 2005

I use Filemon to detect processes that write files.

http://www.sysinternals.com/Utilities/Filemon.html

"Kevin" wrote:

> I originally posted this on an Outlook discussion group, but have since
> realised Security might have been more appropriate, so am copying it here
> with minor additions.
>
> For less than one full day, both NAV and AVG indicated that files that are
> constantly created in "C:/Documents and settings/<user>/Local
> settings/Temp" with names "CC*.tmp" (they appear to be named using
> hexadecimal notation of a byte) have the Netsky.P or .Q worms. Is this
> NAV/NIS creating these files as a result of using MS Outlook, and why would
> the files have an old worm?
>
> Investigating how these worms work shows that the system does not appear
> to be infected with these worms. But the "CC*.tmp" files are always being
> recreated.
>
> Any suggestions how to eliminate the problem?
>
> For further information, warning messages from AVG and NAV only now appear
> when I access that folder/files to try to solve the problem. Maybe there's no
> real problem after all. But if NAV/NIS is creating those files, then why
> would it be creating them with an apparent security flaw?
>
> Kevin