Skip to content
KitploitKITPLOIT
ToolsBlog
Submit
ToolsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

··Feeds·Contact·Privacy·© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
GhostTrace — Read-only Windows forensic scanner for software traces — persistence, execution artifacts (Prefetch, Shimcache, BAM), user activity and Ghost Tasks correlation. 20+ modules mapped to MITRE ATT&CK. | Kitploit
Tools/GitHubGitHub/devzinh/ghosttrace
Memory ForensicsPersistence MechanismsForensicsDigital ForensicsThreat IntelligenceIncident Response
GitHubdevzinh/ghosttrace

GhostTrace

Read-only Windows forensic scanner for software traces — persistence, execution artifacts (Prefetch, Shimcache, BAM), user activity and Ghost Tasks correlation. 20+ modules mapped to MITRE ATT&CK.

View Repository
26 days agoNot yet reviewed

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share
Website

GhostTrace

GhostTrace

Find what software left behind on Windows, before it finds its way back.

GhostTrace is a local Windows forensic trace hunter for incident responders, system administrators, and security-minded power users. It maps persistence, execution, activity, and leftover artifacts into a reviewable record, then offers tightly constrained cleanup only when you explicitly choose it.

CI Release Windows .NET License

Download | Quick start | Capabilities | Safety model | Roadmap | Portuguese (Brazil)


Why GhostTrace

Uninstalling an application does not always remove its operational footprint. Startup entries, scheduled tasks, cached execution evidence, registry values, services, and folders can remain long after the installer reports success.

GhostTrace turns that broad question into a focused, local investigation:

  • One focused hunt across 22 forensic modules.
  • Evidence by source, with findings, errors, and metadata kept per module.
  • Offline by design, with no telemetry, uploads, or cloud dependency.
  • Audit-ready output, including TXT records, JSON outputs for directed collectors, and cleanup logs.
  • Human-controlled cleanup, never automatic remediation.

GhostTrace running in the terminal

Quick start

Install

Download the latest x64 MSI from Releases:

root@kitploit:~
GhostTrace-<version>-x64.msi

The package is self-contained, so the target machine does not need a pre-installed .NET runtime. Run GhostTrace as Administrator to access protected Windows artifacts.

Hunt a software name

root@kitploit:~
GhostTrace.CLI scan --name nvidia

The interactive flow shows progress, groups findings by technique, and can export a record of the investigation. If safe cleanup candidates exist, you must select them and type a confirmation phrase before any removal occurs.

Run it in automation

root@kitploit:~
GhostTrace.CLI scan --name nvidia --quiet --output C:\Cases\Host1

--quiet creates a non-interactive TXT record. A report write failure returns a non-zero exit code, so automation does not silently succeed without an artifact.

Essential commands

Choose the interface language with --lang:

root@kitploit:~
GhostTrace.CLI scan --name nvidia --lang en
GhostTrace.CLI --lang pt-BR

From collection to review

GhostTrace investigation workflow

  1. GhostTrace runs the modules available for the selected collection.
  2. Each module returns its own findings, errors, and metadata.
  3. The CLI renders a concise summary and writes a local record when requested.
  4. Any selected cleanup operation is written to a separate audit log.

What it collects

GhostTrace module coverage

Persistence modules

Execution and activity modules

Forensic safety

GhostTrace is a read-only collector by default. Its cleanup workflow targets software leftovers, not automatic malware remediation.

  • No network calls, telemetry, evidence upload, or cloud account is required.
  • Cleanup starts with no preselected item and requires explicit selection plus typed confirmation.
  • Execution caches and activity histories are never cleanup candidates.
  • A directory is removable only when it is directly under a trusted root, exactly matches the target name, and is not a junction or symlink.
  • Partial name matches become FilesystemTraceHint: reportable, never removable.
  • JSON reports are written atomically, preserving an existing report until a replacement completes.
  • Ctrl+C cooperatively cancels scheduled-task correlation and Prefetch file reading.

A finding is evidence, not a verdict. Interpret it with the host timeline, your environment, and your incident-response process.

Outputs that fit the investigation

OutputBest for
Interactive tableFast analyst review
TXT report

PartialSuccess means a module produced findings but also encountered a limitation. Read that module's errors before treating an absent result as a clean source.

Built to be trusted

  • Pull requests restore, build, and test on Windows with .NET 10.
  • The release gate tests the full GhostTrace.sln before building the MSI.
  • Both src/GhostTrace.Tests and tests/GhostTrace.Tests.Unit are included in the solution and CI.
  • Stable releases accept only v<major>.<minor>.<patch> tags.
  • GhostTrace is released under the MIT License.

Star history

GitHub Repo stars Star History

Track the project's public star history on Star History.

Documentation

  • Scheduled Tasks Correlation Playbook
  • Product roadmap
  • UX and architecture decisions
  • Test project guide
  • README in Portuguese (Brazil)

Contributing

Contributions are welcome. Keep collectors read-only, propagate CancellationToken, surface coverage gaps as result errors, and include tests with behavior changes. The roadmap highlights the next high-impact areas.


GhostTrace supports investigation. Validate every artifact in the context of the host, its timeline, and your operating procedures.

Download Tool
GoalCommand
Open the interactive menuGhostTrace.CLI
Run a full triageGhostTrace.CLI scan
Hunt a named applicationGhostTrace.CLI scan --name <name>
Write a script-friendly scan recordGhostTrace.CLI scan --name <name> --quiet --output <directory>
Correlate Task Scheduler COM and TaskCacheGhostTrace.CLI scan-tasks-correlate-json --output <report.json>
Inspect a directory, Registry key, or Event Logscan-fs-json, scan-reg-json, scan-evt-json
Area
Evidence sources
PersistenceRun/RunOnce, Startup, services, Winlogon, IFEO, AppInit, LSA, Active Setup, WMI, and scheduled tasks
ExecutionPrefetch, Shimcache, BAM/DAM, UserAssist, and MUICache
User activityPowerShell history, outbound RDP history, RecentDocs, USB, and network artifacts
Installed software and leftoversUninstall entries, StartupApproved, Program Files, ProgramData, and AppData traces
Scheduled task correlationCOM and TaskCache discrepancies used to investigate Ghost Tasks (T1053.005)
ModuleSource
PersistenceScanModuleRun/RunOnce and Startup folders
ServicesScanModuleService and driver ImagePath values
AsepScanModuleWinlogon, IFEO, AppInit, LSA, and Active Setup
ScheduledTasksScanModuleTask Scheduler COM, including hidden tasks
TaskCacheScanModuleTaskCache\Tree anomalies
WmiPersistenceScanModule__EventFilter, __EventConsumer, and bindings
ModuleSource
PrefetchScanModuleWindows 10/11 .pf files, including XPRESS-Huffman compression
ShimcacheScanModuleAppCompatCache
BamScanModuleBAM/DAM records by SID
UserAssistScanModuleGUI launches and usage counts
MuiCacheScanModuleShell MUICache
PowerShellHistoryScanModulePSReadLine history and suspicious command signals
RdpConnectionScanModuleOutbound RDP connection history
RecentDocsScanModuleExplorer RecentDocs
UsbDeviceScanModuleUSBSTOR history
NetworkArtifactsScanModuleHosts file and known network profiles
Local record from scan, including --quiet automation
JSON reportDirected collectors and scheduled-task correlation
Cleanup logAuditing removed, skipped, and failed cleanup actions