Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Possible security intrusion or profiling?

Status
Not open for further replies.

vop

Technical User
Mar 30, 2001
360
CA
Potential phone home content holders?

Directory of C:\WINDOWS

FFFE10~1 TMP 0 03-06-04 11:08p fffe101f_{3403CDC0-6FC3-11D8-96A2-00E0299E2939}.tmp
FFFE10~2 TMP 0 03-06-04 11:08p fffe101f_{3403CDC1-6FC3-11D8-96A2-00E0299E2939}.tmp
FFFE2C~1 TMP 0 03-06-04 11:37p fffe2ce3_{4A2148E0-6FC7-11D8-96A2-00E0299E2939}.tmp
FFFE2C~2 TMP 0 03-06-04 11:37p fffe2ce3_{4A2148E1-6FC7-11D8-96A2-00E0299E2939}.tmp
FFFED6~1 TMP 0 03-07-04 12:06a fffed6c1_{3C7E8B40-6FCB-11D8-96A2-00E0299E2939}.tmp
FFFED6~2 TMP 0 03-07-04 12:06a fffed6c1_{3C7E8B41-6FCB-11D8-96A2-00E0299E2939}.tmp

Very recently, every time I boot I have been consistently getting a suspicious looking pair of 0K files in the C:\windows directory (WIN98). I found them in my regular cleanup check for *.tmp files (using file>find). They are of the pattern fff*.tmp and appear to be initialized at startup.

Might anyone have some idea as to what these files are or of their potential source? They almost look like registry type references.

I religiously update and run:
Norton Anti-Virus
SpyBlocker, SpyBot, Ad-aware, and PestPatrol
The Cleaner - trojan scanner
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top