Study guide
18.4 Browser Artifact Recovery, Private Browsing, USB Enumeration, Partition Recovery & Packer Unpacking Tools
Computer Hacking Forensic Investigator CHFI 312-49
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Foundations of Digital Forensics & Cybercrime Investigation
1.1 Cybercrime Classifications, Forensic Science Principles & Legal Admissibility 1.2 RFC 3227 Order of Volatility, Live vs. Dead Acquisition & Forensic Readiness 1.3 Indicators of Compromise (IoCs), Cyber Attribution & Threat Intelligence 1.4 AI-Assisted Forensics, GitOps, Automation/Orchestration & Forensics-as-a-Service (FaaS)
2 Chapter 2: Modern Forensic Environments & Emerging Threats
2.1 Fileless Malware, In-Memory Execution & Living-off-the-Land (LotL) 2.2 IoT & Operational Technology (OT/SCADA) Forensic Fundamentals 2.3 Dark Web, Tor Network, Onion Routing & Hidden Services Forensics 2.4 Blockchain Transactions, Cryptocurrency Tracing & Digital Asset Investigations
3 Chapter 3: Legal Frameworks, Search Warrants & Evidence Rules
3.1 Federal Rules of Evidence (FRE 702, 901, 902, 1001-1003) & Daubert/Frye Standards 3.2 Fourth Amendment, Warrant Exceptions, Workplace Search & Consent Protocols 3.3 International Standards: ISO/IEC 27037, ACPO Principles & ENFSI Guidelines 3.4 Cybercrime Statutes, Privacy Compliance, CAN-SPAM & International Cooperation
4 Chapter 4: eDiscovery, Chain of Custody & Professional Ethics
4.1 Electronic Discovery Reference Model (EDRM) & Legal Spoliation Holds 4.2 Chain of Custody Documentation, Evidence Packaging & Tamper-Evident Handling 4.3 Expert Witness Testimony, Report Writing Standards & EC-Council Code of Ethics
5 Chapter 5: Storage Architecture, Boot Sequences & Media Forensics
5.1 Storage Media Architecture: Sectors, Clusters, RAM/File Slack & Unallocated Space 5.2 Partition Tables & Boot Structures: MBR, GPT, VBR, BIOS vs. UEFI Secure Boot 5.3 RAID Reconstruction (RAID 0, 1, 5, 6, 10) & SSD Forensic Challenges (TRIM, Wear Leveling)
6 Chapter 6: Windows File Systems: NTFS & FAT
6.1 NTFS Architecture: Master File Table ($MFT) Record Structure & Attribute Headers 6.2 NTFS Artifacts: Alternate Data Streams (ADS), Volume Shadow Copies (VSS) & $LogFile 6.3 FAT12/16/32 and exFAT Architecture, Directory Entries & File Deletion Mechanics
7 Chapter 7: Non-Windows File Systems & File Signatures
7.1 Linux File Systems: ext2/ext3/ext4 Inode Architecture, Superblocks & Journaling Forensics 7.2 macOS File Systems: HFS+ and Apple File System (APFS) Architecture & Snapshots 7.3 File Signatures, Magic Bytes, Hex Headers/Footers & File Carving Techniques
8 Chapter 8: Investigation Lifecycle, Lab Setup & First Response
8.1 Forensic Laboratory Accreditation: ISO/IEC 17025 Standards & Hardware/Software Controls 8.2 First Responder Duties: Crime Scene Containment, Electronic Triage & Volatile Triage 8.3 Physical Evidence Packaging, Anti-Static/Faraday Protection & Transport Security
9 Chapter 9: Forensic Acquisition & Verification Methodology
9.1 Hardware and Software Write-Blockers: Operational Validation & Bridge Verification 9.2 Bit-Stream Disk Imaging, Physical vs. Logical vs. Targeted Acquisition Methodology 9.3 Forensic Image Formats (RAW/DD, E01, AFF) & Cryptographic Hashing Verification (MD5, SHA-256)
10 Chapter 10: Anti-Forensics Techniques & Countermeasures
10.1 Steganography Detection: Spatial/Frequency Domain Steganalysis & Hidden Carrier Extraction 10.2 Timestomping Countermeasures: Comparing $STANDARD_INFORMATION vs $FILE_NAME Timestamps 10.3 Secure Wiping, Degaussing, File Shredding Countermeasures & Residual Artifact Recovery
11 Chapter 11: Windows Operating System Forensics
11.1 Windows Registry Forensics: SYSTEM, SOFTWARE, SAM & NTUSER.DAT Hive Analysis 11.2 Execution Artifacts: Prefetch (.pf), Shimcache (AppCompatCache), Amcache.hve & UserAssist 11.3 User Activity Artifacts: ShellBags, LNK Shortcut Files, Jump Lists & Recycle Bin ($I/$R) 11.4 Windows Event Log Forensics: Security Audit IDs (4624, 4625, 4688, 4720, 7045) & EVTX Parsing
12 Chapter 12: Memory Forensics & Malware Analysis
12.1 Volatile Memory Acquisition: RAM Capture, Crash Dumps, Hiberfil.sys & Pagefile.sys 12.2 Memory Analysis with Volatility 3: pslist, pstree, malfind, netscan & Vadinfo 12.3 Static Malware Triage: Strings, PE Headers, Import Tables, Hashes & YARA Rule Matching 12.4 Dynamic Malware Analysis: Sandboxing, Process Monitor (Procmon), Regshot & Network Callouts 12.5 .NET Managed Malware Analysis & the GOOTLOADER Fileless Infection Chain
13 Chapter 13: Network, Web Application & Email Forensics
13.1 Network Forensics: PCAP Analysis, Protocol Dissection, Snort/Suricata & Flow Analysis 13.2 Web Server Forensics: Apache/IIS Access Logs, SQL Injection, XSS & Web Shell Detection 13.3 Email Forensics: RFC 5322 Headers, Authentication (SPF, DKIM, DMARC) & Mbox/PST Extraction 13.4 SIEM Event Correlation, Cross-Source Timeline Analysis & Super-Timeline Construction 13.5 Investigating Directory Traversal, Command Injection, Parameter Tampering, XXE, Cookie Poisoning & Brute Force 13.6 Network Device & Service Log Forensics: Firewall, IDS, Honeypot, Router, DHCP, Switch, VPN, DNS & SSH 13.7 Wireless Network Forensics: Rogue APs, Evil Twins, MAC Spoofing, Deauthentication & Jamming
14 Chapter 14: Mobile, Cloud & IoT Forensics
14.1 Mobile Device Forensics: Manual, Logical, File System & Physical Extraction (Android/iOS) 14.2 Mobile Artifact Analysis: Call Logs, SMS/Chat SQLite Databases, Location Data & Plists 14.3 Cloud Forensics: AWS CloudTrail, Azure Activity Logs & Multi-Tenant Evidence Collection 14.4 IoT Forensics: UART/JTAG Physical Interfaces, Firmware Extraction & Sensor Telemetry
15 Chapter 15: Commercial & Open-Source Forensic Suites
15.1 Commercial Forensic Platforms: EnCase Forensic, FTK (Forensic Toolkit) & FTK Imager 15.2 Open-Source Forensic Platforms: Autopsy, The Sleuth Kit (TSK) & SIFT/CAINE Workstations 15.3 Specialized DFIR Utilities: Eric Zimmerman Tools (EZ Tools) & Sysinternals Forensic Suite
16 Chapter 16: Analysis Toolkits, Python Scripting & Tool Validation
16.1 Reverse Engineering & Password Cracking: Ghidra, IDA Pro, Hashcat & John the Ripper 16.2 Python for Digital Forensics: Parsing Raw Artifacts, Custom Scapy Scripts & Evidence Automation 16.3 Forensic Tool Testing & Validation: NIST CFTT Methodology, ISO/IEC 17025 Standards & Daubert Compliance
17 Chapter 17: Database Forensics & Web Application Firewalls
17.1 MySQL Forensics: Internal Architecture, Data Directory, Information Schema & Utility Programs 17.2 SQL Server Forensics: SSMS, ApexSQL, SQLCMD Transaction-Log Collection, Plan Cache & Trace Files 17.3 Web Application Firewall (WAF) Architecture, Audit Logs, Benefits & Limitations
18 Chapter 18: Social, Virtualized, Multimedia & Browser Investigations
18.1 Social Media, Social Engineering, Insider Threat & Identity Theft Forensics 18.2 Virtualization, Container & Microservices Forensics, Bluetooth and Electron Chat Applications 18.3 Multimedia Forensics: Image, Audio & Video Authentication, EXIF, PRNU and Deepfake Detection 18.4 Browser Artifact Recovery, Private Browsing, USB Enumeration, Partition Recovery & Packer Unpacking Tools
18.4 Browser Artifact Recovery, Private Browsing, USB Enumeration, Partition Recovery & Packer Unpacking Tools
Key Takeaways Explain This Topic AI
Chromium-based browsers store history, downloads, cookies, and autofill in SQLite databases under the User Data profile directory and timestamp them in WebKit time, which counts microseconds since 1601-01-01 UTC, while Firefox uses places.sqlite with PRTime microseconds since the Unix epoch.
Private and incognito browsing writes no history to disk, but the session survives in RAM, the pagefile and hibernation file, the DNS resolver cache, and $UsnJrnl and $LogFile records of the temporary cache files that were created and deleted.
USB device history is reconstructed from USBSTOR for vendor, product and serial, MountedDevices for the drive letter binding, and setupapi.dev.log for the first-ever connection timestamp, and PowerShell can enumerate all three from a mounted image hive.
Partition recovery tools such as TestDisk rebuild a damaged or deleted partition table by scanning for file system boot sectors and superblock backups, which recovers a whole volume that appears as raw unallocated space.
Program packers compress and encrypt an executable so static analysis sees only the stub; unpacking tools and memory dumping at the original entry point restore the analyzable payload.
Last updated: September 2026
18.4 Browser Artifact Recovery, Private Browsing, USB Enumeration, Partition Recovery & Packer Unpacking Tools
Quick Answer: Blueprint Domain 6 names tools to examine the cache, cookie, and history recorded in web browsers , private browsing and browser artifact recovery , USB device enumeration using Windows PowerShell , partition recovery tools , and program packers unpacking tools . Two facts anchor the section: Chromium timestamps are WebKit time — microseconds since 1601-01-01 UTC , while Firefox uses PRTime — microseconds since the Unix epoch ; and private browsing is not private to a forensic examiner , because RAM, the pagefile, the hibernation file, the DNS cache, and NTFS journal records all retain traces.
- Browser Artifact Locations and Schemas
- Chromium Family (Chrome, Edge, Brave, Opera, Vivaldi)
Profile base: %LocalAppData%\Google\Chrome\User Data\Default\ (Edge substitutes Microsoft\Edge ).
File Type Key tables / contents
History SQLite urls (url, title, visit_count , typed_count , last_visit_time), visits (visit_time, transition type), downloads , downloads_url_chains , keyword_search_terms
- Cookies SQLite host_key, name, encrypted_value , creation_utc, expires_utc, last_access_utc
- Login Data SQLite origin_url, username_value, password_value (DPAPI/AES-GCM protected)
- Web Data SQLite autofill entries, credit-card and address profiles
- Top Sites , Favicons , Shortcuts SQLite Frequency ranking, favicon cache, omnibox shortcuts
- Cache\ Simple Cache index , data_0 – data_3 , and per-entry f_###### files holding cached resources
Sessions\ Binary Session_* and Tabs_* — open tabs and navigation stacks at last close , including private-window-adjacent state
- Preferences , Secure Preferences JSON Installed extensions, sync account, homepage, search engines
- Network\Network Persistent State JSON Hosts recently connected to, including over QUIC
The typed_count column deserves attention. A URL with a non-zero typed_count was manually typed into the address bar , which distinguishes intentional navigation from a redirect or an embedded resource — a distinction that matters enormously in possession and intent cases. The visits.transition value carries the same information at per-visit granularity ( LINK , TYPED , AUTO_BOOKMARK , RELOAD , FORM_SUBMIT ).
Firefox
Profile: %AppData%\Mozilla\Firefox\Profiles\<random>.default-release\ .
File Contents
places.sqlite moz_places (URL, title, visit_count, frecency) joined to moz_historyvisits (visit_date, visit_type); also bookmarks
- cookies.sqlite , formhistory.sqlite , permissions.sqlite Cookies, form autofill, per-site permissions
- cache2\entries\ Cache entries, each with a metadata trailer holding the source URL and fetch time
- sessionstore-backups\recovery.jsonlz4 Open tabs and full back/forward history , compressed with mozlz4
- logins.json + key4.db Saved credentials and the NSS key database
- Legacy Internet Explorer / Edge Legacy
WebCacheV01.dat is an ESE (Extensible Storage Engine) database holding history, cache, cookies, and download records in container tables. Parse with esedbexport , ESEDatabaseView , or a dedicated parser; dirty databases may need esentutl /r recovery against a working copy only. Older systems use index.dat .
Timestamp Formats — the Recurring Trap
- Browser Epoch Unit
- Chromium (WebKit time) 1601-01-01 00:00:00 UTC Microseconds
- Firefox (PRTime) 1970-01-01 00:00:00 UTC Microseconds
Safari (Cocoa/Mac absolute) 2001-01-01 00:00:00 UTC Seconds (often fractional) -- Chromium History: convert WebKit time to a readable UTC timestamp
- SELECT url, title, visit_count, typed_count,
- datetime(last_visit_time/1000000 - 11644473600, 'unixepoch') AS last_visit_utc
- FROM urls ORDER BY last_visit_time DESC;
The constant 11,644,473,600 is the number of seconds between 1601-01-01 and 1970-01-01. Applying the Firefox conversion to a Chromium value — or omitting the offset — produces timestamps centuries adrift, and it is one of the most common avoidable errors in browser timeline work.
Tooling
- Tool Role
- Hindsight Chromium-focused parser producing a unified timeline across history, cache, cookies, and extensions
- NirSoft suite (BrowsingHistoryView, ChromeCacheView, MZCacheView, IECacheView) Fast per-artifact triage
- DB Browser for SQLite Manual schema exploration — open read-only
- Autopsy / Magnet AXIOM / Belkasoft Integrated multi-browser recovery including deleted records
- sqlite3 + .recover , or WAL/journal carving Recover deleted rows from -wal and -journal files
Important
Always collect the -wal and -shm files alongside every browser SQLite database. In WAL mode, recent transactions — including records the browser has "deleted" — live in the write-ahead log and have not yet been merged into the main database. Copying only History without History-wal silently discards the most recent and most relevant activity.
Private Browsing: What Actually Survives
Incognito and Private Browsing suppress disk writes of history, cookies, and cache for the session. They do not make the session invisible.
Residue Why it exists
RAM The full session — URLs, page DOM, form contents, and often credentials — is in the browser process memory. A memory image recovers it directly with string and URL carving.
pagefile.sys / swapfile.sys Memory paged to disk under pressure retains fragments after the browser exits
hiberfil.sys Hibernation writes all of RAM to disk; a hibernation file created during or after a private session is effectively a frozen memory image
DNS resolver cache ipconfig /displaydns on a live system lists names resolved regardless of browsing mode (volatile — lost on reboot or flush)
$UsnJrnl and $LogFile NTFS journals record the creation and deletion of the temporary cache files the private session used, proving activity and its timing even though the content is gone
- $MFT resident remnants Small deleted temporary files may retain resident data in their MFT records
- Browser crash dumps / recovery files A crash during a private session can persist session state
Network- and endpoint-side records Proxy logs, EDR telemetry, and firewall records are entirely unaffected by browsing mode
Important
Private browsing changes only what the browser writes. It changes nothing about what the operating system, the network, or the memory subsystem retain. Where the private session is the crux of the case, memory acquisition is the priority action and hiberfil.sys is the fallback if the machine has already been powered down.
USB Device Enumeration with Windows PowerShell
The triangulation from three artifacts is the standard method:
Artifact Yields
SYSTEM\CurrentControlSet\Enum\USBSTOR\<Ven_Prod_Rev>\<serial> Vendor, product, revision, device serial number , FriendlyName
- SYSTEM\CurrentControlSet\Enum\USB\VID_xxxx&PID_xxxx USB VID/PID; the interface-level view of the same device
- SYSTEM\MountedDevices Binds a drive letter and volume GUID to the device
%windir%\INF\setupapi.dev.log First-ever connection timestamp — plain text, and the authoritative "first seen" source
- SOFTWARE\Microsoft\Windows Portable Devices\Devices Volume label and friendly name
- NTUSER.DAT MountPoints2 Which user account mounted the volume
Microsoft-Windows-DriverFrameworks-UserMode/Operational (when enabled) Connect and disconnect event pairs # Live host: currently and previously enumerated USB storage devices
- Get-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Enum\USBSTOR\*\*' |
- Select-Object FriendlyName, PSChildName, Service, ContainerID
- # Present-state view including removed devices
- Get-PnpDevice -Class USB -Status OK,Unknown |
- Select-Object FriendlyName, InstanceId, Status
- # Mounted image: load the exported SYSTEM hive under a temporary key and query it offline
- reg load HKLM\EvidenceSYSTEM E:\evidence\SYSTEM
- Get-ChildItem 'HKLM:\EvidenceSYSTEM\ControlSet001\Enum\USBSTOR' -Recurse |
- Select-Object Name
- reg unload HKLM\EvidenceSYSTEM
# First-connection times straight out of setupapi.dev.log
Select-String -Path 'C:\Windows\INF\setupapi.dev.log' -Pattern 'Device Install \(Hardware initiated\).*USBSTOR' -Context 0,2
Serial-number caveat: the second character of a USBSTOR serial being & indicates the device did not report a hardware serial and Windows generated an instance identifier instead. Such an identifier is host-specific , so it cannot be used to prove the same device was connected to a different machine.
Partition Recovery Tools
When a partition table is wiped, corrupted, or overwritten, an entire volume appears as raw unallocated space. Partition recovery works by scanning the raw device for file system signatures — NTFS and FAT boot sectors, ext superblock backups, HFS+/APFS volume headers — and rebuilding the table from what it finds.
Tool Notes
TestDisk Open-source, cross-platform; Analyse then Deeper Search rebuilds MBR/GPT entries; also rewrites a damaged NTFS boot sector from its backup copy at the end of the partition
- PhotoRec TestDisk's companion; ignores the file system entirely and carves files by signature
- gdisk / sgdisk Repairs GPT from the backup GPT header at the end of the disk
- Active@ Partition Recovery, EaseUS, MiniTool Commercial GUI equivalents
Autopsy / TSK mmls Enumerates partitions and gaps; mmls showing a large unallocated region where a volume should be is the first indicator
Warning
Run recovery only against a working copy of the image, never the original evidence or the original media. TestDisk in write mode alters the partition table. The forensically sound sequence is: image → hash → duplicate the image → run recovery on the duplicate → document the change → re-verify the original's hash is unchanged.
GPT's built-in redundancy is the examiner's friend: a primary GPT header destroyed at LBA 1 has a backup copy in the final sector of the disk, so a "destroyed" GPT disk is often recoverable in a single step.
Program Packers and Unpacking Tools
A packer compresses and/or encrypts an executable and prepends a stub that reconstructs the original in memory at run time. The blueprint lists program packers among anti-forensics techniques and lists program packers unpacking tools in the tool domain.
Identifying a Packed Binary
Indicator Detail
High section entropy Compressed or encrypted sections approach 8.0 bits per byte; entropy above roughly 7.0 is a strong flag
- Abnormal section names UPX0 / UPX1 , .aspack , .themida , .vmp0 , or random names
- Tiny import table Typically only LoadLibraryA and GetProcAddress — imports are resolved at run time
Raw size far below virtual size A section with SizeOfRawData near zero but a large VirtualSize is the unpacking destination
- Entry point outside .text The entry point sits in the last section
- Almost no readable strings Static strings output collapses to stub text only
Detection tools: Detect It Easy (DiE) , PEiD (legacy signatures), PEStudio , ExeinfoPE , pefile plus an entropy script in Python.
Unpacking Approaches
Native unpacker — UPX ships upx -d , which cleanly restores a genuinely UPX-packed file. Attackers often modify UPX headers specifically to break this.
Dynamic unpacking (the general method) — run the sample in an isolated, instrumented VM and dump the process from memory once the stub has reconstructed the payload at the original entry point (OEP) , then rebuild the import table. Tools: x64dbg with the Scylla import reconstructor, OllyDumpEx , PE-sieve and HollowsHunter (which detect and dump implanted or hollowed modules automatically).
Emulation / sandbox unpacking — unipacker , Qiling, and sandbox platforms that snapshot memory after unpacking.
Memory-image extraction — where only a RAM image exists, Volatility's malfind and VAD dumping recover the unpacked image in exactly the same way described for reflective .NET loading in Section 12.5.
Commercial protectors (Themida, VMProtect, Enigma) go beyond packing into code virtualization , translating the original instructions into a custom bytecode interpreted by an embedded VM. These are not "unpacked" in any straightforward sense; analysis proceeds by behavioral observation and by targeted devirtualization, which is expert-level work and should be scoped accordingly.
Detecting Data Hiding in File System Structures with OSForensics
The blueprint names one product for this task specifically: OSForensics from PassMark Software . It matters here because concealment rarely uses one technique in isolation — a single case may combine a renamed executable, a payload parked in an alternate data stream, and a deleted staging file — and OSForensics puts the corresponding searches in one workflow over a mounted image.
Module What it exposes The hiding technique it defeats
Alternate data stream listing and search Enumerates and searches named $DATA streams attached to files and directories Payloads parked in an ADS, which a directory listing and a file-size check both miss (Section 6.2)
Mismatch File Search Finds files whose contents do not match their declared extension Extension renaming — the magic-byte contradiction taught in Section 7.3
Deleted Files Search Recovers files a user attempted to destroy, by walking file-system metadata for unlinked entries Ordinary deletion, which unlinks the record but leaves the clusters intact (Section 10.3)
Raw Disk Viewer Navigates and searches the raw bytes of a volume outside the file-system abstraction Data parked in file slack, volume slack, and unallocated space
File indexing and search Builds a ranked index across hundreds of file types for keyword search Content buried in large archives and document sets that no manual review would reach
Hash verification and hash-set matching Verifies and matches files by MD5, SHA-1, and SHA-256 Known-file elimination, and proving that a recovered copy is bit-identical to the original
Two practical cautions carry into the exam. First, an ADS or mismatch hit is a lead, not a finding — the examiner opens the stream or the header and reads what is actually there, because legitimate software writes both benign streams (the Zone.Identifier mark-of-the-web discussed in Section 6.2) and files whose extensions are genuinely unconventional. Second, the tool-validation rule from Section 16.3 applies with full force to concealment claims: a hiding allegation that rests on a single automated scan is corroborated with a second, independently validated tool before it reaches a report, which is also the defense against the anti-forensic technique of feeding a parser malformed structures.
Detecting overwritten data and metadata is the same problem viewed from the other end. Where a file has been overwritten in place, the surviving proof is circumstantial and lives in the structures around it: $LogFile and $UsnJrnl transaction entries naming the file, an $MFT record whose $STANDARD_INFORMATION and $FILE_NAME timestamps disagree, a Volume Shadow Copy or APFS snapshot predating the overwrite, and Prefetch or Amcache evidence that a wiping utility ran at all.