Zone.Identifier fil...
 
Notifications
Clear all

Zone.Identifier files

4 Posts
4 Users
0 Likes
1,538 Views
(@jakeaw03)
Posts: 65
Trusted Member
Topic starter
 

I have a piece of identified malware located in the system32 dir. In the same directory is a file with the same malware name plus a "Zone.Identifier", example foo.exe.Zone.Identifier. The contents of the file is [zonetransfer] Zoneid=3

http//www.sandersonforensics.com/Files/ZoneIdentifier.pdf
Says that is an ADS.

http//www.f-secure.com/v-descs/zoneident.shtml
Says, Existance of Zone.Identifier stream on some files is normal, and as such is of no cause for concern. This stream is generated by Internet Explorer and Outlook when saving files from to local disk from different security zones.

So what is my question? What does this mean for me forensically? From what I have read it doesn't really mean anything. I am interested now the original malware got on the system, and from what I read in the F-secure posting it has something to do with saving the original file via outlook, or could be.

Thanks,

 
Posted : 31/10/2008 11:59 pm
keydet89
(@keydet89)
Posts: 3568
Famed Member
 

So what is my question? What does this mean for me forensically? From what I have read it doesn't really mean anything. I am interested now the original malware got on the system, and from what I read in the F-secure posting it has something to do with saving the original file via outlook, or could be.

I think you answered your own question already…"This stream is generated by Internet Explorer and Outlook when saving files from to local disk from different security zones."

Well, it should read "…when saving files to the local disk…", rather than "…from to…", but that's your answer.

How large are the ADS? Around 28 bytes or so? What are the contents of the ADSs?

 
Posted : 01/11/2008 4:34 pm
(@spawn)
Posts: 34
Eminent Member
 

I think http//support.microsoft.com/kb/883260/ has the explanation you might be looking for.

 
Posted : 03/11/2008 2:57 am
(@arbert)
Posts: 14
Active Member
 

I think the biggest impacts "forensically" are 1. It tells you where windows "thought" the file was opened from and 2. It dictates the files were created after August 2004 (release of XP service pack 2 which introduced the use of the feature).

I just completed a case where I was baffled for a bit because I had some files create 2001-2004 and they all had ZIDs attached to them…..

 
Posted : 03/11/2008 3:21 am
Share: