Artifact/Program Version
VLC is a free and open source cross-platform multimedia player and framework that plays most multimedia files as well as DVDs, Audio CDs, VCDs, and various streaming protocols.

ActionVoip is a program to make VOIP calls from the a PC or a Smart phone. It is used by thousands of users worldwide to make free/cheap phones calls. It is not mandatory for a user to provide their identity information while making a call. The user ID shown on the receiving phone is usually an “Unknown” number.

Registry Keys

HKU\<<>>\Software\ActionVoip\ActionVoip\Accounts\Password: <<>>

HKU\<<>>\Software\ActionVoip\ActionVoip\Accounts\Username: “<<>>”

HKU\<<>>\Software\ActionVoip\ActionVoip\CallHistory\<<>>\Count: 0x00000002 —> REG_DWORD value showing the number of calls made from the account

“Windows Essentials” – from Wikipedia:“Windows Essentials (formerly Windows Live Essentials and Windows Live Installer) is a suite of freeware applications by Microsoft that aims to offer integrated and bundled e-mail, instant messaging, photo-sharing, blog publishing, and security services. Essentials programs are designed to integrate well with each other, with Microsoft Windows, and with other Microsoft web-based services such as SkyDrive and Outlook.com, so that they operate as a “seamless whole”.Windows Essentials 2012 includes the following applications:
Windows Live Messenger
Windows Photo Gallery
Windows Movie Maker
Windows Live Mail
Windows Live Writer
SkyDrive for Windows
Outlook Connector Pack
Windows Live Family Safety (Windows 7 only)

Artifact Description
Skype is a popular instant messaging, audio, and video teleconferencing program. The Skype application data directory contains a file named shared.xml. As the extension implies, the file is XML formatted, but most of the entries are encoded. This encoding has not been documented or reversed to my knowledge.

Of interest is one of the non-encoded fields, set off with the <ContraProbeResults> tag. This tag contains a list with an IP address and varying port numbers:

Testing shows that the IP address reflects the “externally visible” IP address of the workstation where Skype is running– in other words the IP address of the outermost NAT gateway connecting the device to the Internet. There is no documentation from Skype related to the contents of the shared.xml file, so this finding is based purely on observation. Eoghan Casey references this artifact in his “Handbook of Digital Forensics and Investigation” but makes no conclusive statements regarding its meaning.

This artifact can be useful for attribution as it indicates the IP address the computer was connecting to the Internet from as of the last time Skype updated this entry. This may help tie a subject to a particular IP address and activity originating from that address.

Multiple versions of shared.xml may be found in unallocated, indicating that the Skype software sometimes deletes and recreates this file. String searching in unallocated for “<ContraProbeResults>” can turn up historical IP information related to the local system.

Immediately following the <ContraProbeResults> tag are additional encoded entries under the <ProbeResults> list. The individual tags in the list appear to be dates in “Unix Epoch Format” (seconds since Jan 1, 1970) with a leading underscore. While the entries themselves are encoded, hexadecimal IP addresses, possibly followed by 16-bit port numbers, can be observed.

In the example below, you can pick out the encoded form of “71.224.218.86” as “47E0DA56″. The meaning of the rest of the data in each entry is unknown.

If these observations are correct, <ProbeResults> then gives the analyst a time-stamped history of IP addresses used by the local machine when accessing the Internet. Again, this is obviously useful for attribution, as well as indicating networks that the system may have connected to in the past. Simply decode the XML tag to find the date and time, then take the last six bytes of each entry– the first four bytes of the six should be the IP address.

File Locations
\Skype\shared.xml

Research Links
http://books.google.com/books?id=xNjsDprqtUYC&pg=PA56&lpg=PA56&dq=skype+contraproberesults&source=bl&ots=X1xOC47CuG&sig=-npWdZi2I9zCdhgxWAWqHPOLVc8&hl=en&sa=X&ei=pc2bUf-ZLcOjigKVzoF4&ved=0CE0Q6AEwAw#v=onepage&q=skype%20contraproberesults&f=false

Artifact Description
TeamViewer is a program that provides remote desktop software, remote control access, VPN capabilities, file transfers, etc. It can be installed, run temporarily, or used as portable application. One interesting capability is that it can determine if the Remote and Local host are on the same network and it will conduct P2P activity and connect directly, rather than use gateway servers. It is also proxy aware…you can configure it to connect through your network proxies or even a TOR proxy.

While there are important artifacts in the registry, there are a few important files that can help decipher details and events that occurred with the software.

#1 file on Local Host:
C:\Program Files (x86)\TeamViewer\Version8\TeamViewer8_Logfile.log <—–wealth of knowledge in this file

Note: there are more interesting fields in the “TeamViewer8_Logfile.log”, seek it out if you suspect Teamviewer was installed.

Remote Host:
Connections.txt = C:\Users\dude\AppData\Roaming\TeamViewer\Connections.txt <—– this simple file contains the “ID” of the remote host connected to. Fields in this file include date, time connected and date/time disconnected and the user the app ran under.

Local Host:
C:\Program Files (x86)\TeamViewer\Version8\Connections_incoming.txt <—– this simple file contains the “ID” of the remote host that connected to the “local” system. Fields in this file include date, time connected and date/time disconnected and the user the app ran under.

These artifacts contain information you can glean from the registry pertaining to network/PAN services available for the Broadcom Widcomm stack. Further investigation of these artifacts can reveal what was available to other systems. A follow-up post will detail the systems connected.

Extracted from the registry of a Windows 7 x64 system with a Broadcom 2070 Bluetooth radio device.

Registry Keys

-= Primary registry key =-

HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm

-= Bluetooth Services Definitions =-

[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BTConfig\Applications\0001]
“Name”=”Bluetooth Serial Port”
“SecurityId”=dword:00000001
“UUID”=dword:00001101
“GUID”=”{00001101-0000-1000-8000-00805F9B34FB}”
“Authorization”=dword:00000000
“Authentication”=dword:00000001
“Encryption”=dword:00000001
“Description”=”Establish a virtual serial port connection with a remote Bluetooth device. The connection can then be used by any application that supports the COM port number assigned.”
“InstallOnDemand”=dword:00000001
“ComPortNumber”=dword:00000000
“UserInstalled”=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BTConfig\Applications\0008]
“Authorization”=dword:00000000
“Auto”=dword:00000001
“SecurityID”=dword:00000008
“UUID”=dword:00001108
“Authentication”=dword:00000001
“Name”=”Headset”
“Encryption”=dword:00000001
“GUID”=”{00001108-0000-1000-8000-00805F9B34FB}”
“Description”=”Establish an audio connection between this computer and a Bluetooth headset or other remote Bluetooth device acting as a headset. When connected, the remote device can be used as a replacement for this computer’s local microphone and speakers for voice calls (PC telephony) or voice recognition applications.”
“InstallOnDemand”=dword:00000001
“ComPortNumber”=dword:00000000
“UserInstalled”=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BTConfig\Applications\0010]
“Authorization”=dword:00000000
“Auto”=dword:00000001
“SecurityID”=dword:00000011
“UUID”=dword:00001126
“Authentication”=dword:00000001
“Name”=”Printer”
“Encryption”=dword:00000001
“GUID”=”{00001126-0000-1000-8000-00805F9B34FB}”
“Description”=”Add a Bluetooth-enabled printer to your list of available printers. This printer can then be used as if it was physically connected to this computer.”
“InstallOnDemand”=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BTConfig\Applications\0014]
“Name”=”Hands-free Audio”
“Encryption”=dword:00000001
“GUID”=”{0000111E-0000-1000-8000-00805F9B34FB}”
“Description”=”Establish an audio connection between this computer and a Bluetooth headset or other remote Bluetooth device acting as a headset. When connected, the remote device can be used as a replacement for this computer’s local microphone and speakers for voice calls (PC telephony) or voice recognition applications.”
“InstallOnDemand”=dword:00000000
“ComPortNumber”=dword:00000000
“UserInstalled”=dword:00000000
“Authorization”=dword:00000000
“Auto”=dword:00000001
“SecurityID”=dword:00000008
“UUID”=dword:0000111e
“Authentication”=dword:00000001

These artifacts contain information you can glean from the registry pertaining to connected bluetooth devices for the Broadcom Widcomm stack. The connected external Bluetooth devices are broken in to the Bluetooth device MAC addresses in the primary registry entry.
Extracted from the registry of a Windows 7 x64 system with a Broadcom 2070 Bluetooth radio device.

[root]User/xxx/FrostWire
This folder contains five subfolders that contain the actual .torrent files and the actual media that has been downloaded. The subfolders contained within the abovementioned folder are:

•Incomplete: Within this folder, the temporary tracker of the media is saved while in the process of being downloaded, this is the metaphorical bookmark that enables the software to stop and start as the user wishes.
•Saved: This folder contains the artifacts of .torrent files that the user wishes to save- to be able to download at another time.
•Shared: This folder contains all the .torrent trackers that the user has uploaded or created. FrostWirev.5 enables the creation of .torrent trackers.
•Torrent Data: Possibly one of the most important folders, this is where the software saves the actual downloaded media.This is a system automated process, which remains standard.
•Torrent: This folder contains the actual .torrent tracker file, which is the tracker and that is created to download the requested item. For each item downloaded, two entries are created -A .torrent file is created that contain the creation time, the SHA 1 value of the downloaded item, and from where it was downloaded. The second entry created is in unallocated space, which contains the exact same information.
[root]user/xxx/AppData/Roaming/FrostWire

This folder essentially contains a few very important artifacts, which contain important evidentiary information on what was downloaded.

•Createtimes.cache: This cache file contains the SHA-1 value that is assigned to all uploaded media when a .torrent file is created and uploaded to the distribution websites. The SHA-1 value is that of the whole file when it was originally uploaded.This is verified once the item has been downloaded to ensure that the right and complete item has been downloaded.
•Download.dat: This database file contains all the names, identification SHA-1 values of all the files and media downloaded by the user using FrostWire v.5. This can be used to identify what was downloaded when the actual physical items are no longer on the machine.
•Fileurns.cache & Fileurns.bak: These two files essentially contain the same information. When a download is started the software logs the SHA-1 value of the file to ensure that the completed file is downloaded. The SHA-1 value can be used to identify whether a certain item matched the online version of the said file.
•FrostWire.props: This property file contains the selection made by the user upon installation. Here you can determine what changes have been made to the default settings of FrostWire v.5.
•Hostiles.txt: This contains a log of all subnet Masks currently running on the FrostWire v.5 network.
•Library.dat: This database is of all media that is saved by the user to the FrostWire v.5 library, even if it was not physically downloaded onto the machine.

Identifying Searches Done Using FrostWire v.5:
When a user searches for a specific item to download, that search is stored in various places on the local machine:

1.[root]/$Logfile: Contains the search term searched for, where it was found along with the SHA-1 identification hash value.
2.[root]/ProgramData/Microsoft/Search/Data/Applications/Windows/GatherLogs/SystemIndex/SystemIndex.gthr: The header information contained within this gather log, is the search term and how the system and the software communicated.This information is gathered by the two tracing protocols mentioned early Rasapi 32 and RASMANCS.
3.[root]users/xxx/.FrostWire/search_db.h2.db :This is the database that FrostWire v.5 uses to record all searches done by the users.The information recorded is the following:

i. URL Details, where the .torrent file is residing.
ii. The search term searched.
iii. The magnet link and corresponding SHA-1 hash value.
iv. The creation date in Unix that .torrent tracker was created.
4.[root]users/xxx/.FrostWire/search_db/search_db/_28.tii: This is the actual entry in the database for each search term done by the user.This contained what the search term was and the corresponding file ID.
5.[root]users/xxx/.FrostWire/search_db_searchdb__28.tis:This is a record of the search results for the particular search term, meaning that for every .tii file a corresponding .tis file can be found.

Examining a .torrent File and the Artifacts Found:

The file header for .torrent files in hex is:

0x64 38 3A 61 6E 6E 6F 6F 63 65 35 39 (As viewed in hex)

d8:announce59 (As viewed in text)

Contained in this .torrent file is the following information:
File Meaning
http://tracker.torrentbox.com The website that the .torrent file was uploaded to and stored on
2710 The initial port used to communicate to the website initially.
77.247.176.132:80 The IP address communicated with along with the port used for downloading.
1238229350 Unix creation date of the torrent.
Linux Books The name of the item downloaded.
31C8D8C7748C9CC8090C4C2A Identification SHA-1 hash value.

The registry keys SOFTWARE, SECURITY,SYSTEM and the Ntuser.dat were examined and the following artifacts or changes were identified:

1.HKEY/LOCAL MACHINE/SOFTWARE/Current Version: (These changes can be seen in the NTUSER.DAT as well)
This contained the following relevant information of the software FrostWire v.5:
i. Display Name
ii. Publisher
iii. Help Link
iv. URL
v. URL Info
vi. Display Version
vii. Uninstall Command
2.HKEY/LOCAL MACHINE/SOFTWARE/Classes:
This contained the following relevant information of the software FrostWire v.5:
i. FrostWire Toolbar
ii. FrostWire.exe files location.
3. HKEY/LOCAL MACHINE/SOFTWARE/FrostWire:
This contained the following relevant information of the software FrostWire v.5:

i.The executable command used to access and run FrostWire v.5.

4.HKEY/LOCAL MACHINE/SOFTWARE/Tracing:

This contained the following relevant information of the software FrostWire v.5:

i.This contains two tracing mechanisms that Microsoft uses to manage and monitor software, which is the Rasapi 32 command and the RASMANCS command. The information saved is saved in [root]/ProgramData/Microsoft/Search/Data/Applications/Windows/GatherLogs/SystemIndex/SystemIndex.gthr:

5.HKEY/LOCAL MACHINE/SYSTEM:
For FrostWire v.5 to be able to function, a change has to be made within how the system operates:

i.When installing FrostWire v.5, the software automatically change the FireWall policy to create an exception to allow communication from FrostWire v.5 and the downloading servers, thus bypassing the firewall completely.
6.HKEY/LOCAL MACHINE/SECURITY:
No changes could be identified within this registry key.

The AirPort Utility for Windows allows Microsoft computers using Bonjour to access the Apple Time Capsule hard disk. The drive is available as a network share through UNC mapping on your PC. The binary data stored in HKEY_Users\S-1-5-1234567890-1234567890-123456789-1000\Software\AppleInc.\Preferences\com.apple.airport.diskagent will provide confirmation of which volume is associated with your Apple Time Capsule. An external USB connection is available so you could have two volumes listed.

If the end-user setup Windows Backups than you will be able to gain additional insight into the size of the disk with the free space available that may be beneficial in identifying the external USB drive.