Windows artifact analysis toolkit that maps AV detections to PE offsets, sections, RVA/VA and strings, with YARA, AMSI, capa and multi-engine scanning plus JSON/HTML reports.
Correlate static findings and local security-engine verdicts with the exact file offsets, PE addresses, functions, symbols, and source locations that an analyst can review.
Created by St0rn / CybersecurIT
Overview · Capabilities · Quick start · Ghidra · Commands · Development
[!NOTE] SigLens preserves the analyzed artifact. It distinguishes native offsets, exact YARA matches, inferred boundaries, and candidate regions so downstream decisions remain tied to the strength of the available evidence.
SigLens is a local Windows analysis toolkit for artifact triage, false-positive investigation, signature diagnostics, and detection engineering. It combines PE inspection, YARA, AMSI, locally installed AV engines, symbol resolution, and forensic reporting in one CLI and desktop workflow.
| Analyze | Correlate | Review | Report |
|---|---|---|---|
| PE structure, strings, entropy, IOCs, scripts | File offset → section → RVA → VA → function → PDB/source | Hex context, Ghidra bookmarks, engine provenance | Versioned JSON and standalone HTML |
SigLens uses two attribution models:
flowchart LR
A[Artifact] --> B[Static analysis]
A --> C[Local security engines]
B --> D[Offsets and PE mapping]
C --> E[Verdicts and provenance]
D --> F[Function, PDB, source]
D --> G[Ghidra locations]
E --> H[Evidence classification]
F --> I[JSON and HTML report]
G --> I
H --> I
CLEAN, DETECTED, UNKNOWN, UNAVAILABLE, and ERROR states.siglens-report/v1 JSON contract and standalone HTML reports.git clone https://github.com/St0rn/SigLens.git
cd SigLens
.\scripts\Install.ps1 -Dev -AddToUserPath
The installer creates an isolated .venv, installs SigLens and its siglens
console command, detects local integrations, and installs or updates portable
ClamAV unless -SkipAVInstall is supplied. Licensed commercial products are
detected when present and are never installed silently.
If the current PowerShell policy blocks local scripts, apply the policy your organization permits for this process before running the installer.
siglens scan C:\Samples\sample.exe
siglens scan C:\Samples\sample.exe `
--yara .\rules `
--symbol-path .\symbols `
--iocs `
--dissect `
--capa `
--amsi `
--engines .\engines.json
Reports are written to reports\ as JSON and HTML.
siglens pe-security C:\Samples\sample.exe
siglens pe-security C:\Samples\sample.exe --output .\reports\sample-pe.json
The command reports image mitigations and the evidence needed to interpret them, including whether ASLR has usable relocations. It highlights executable and writable sections, entry points outside executable sections, malformed certificate-table bounds, TLS callbacks, debug/PDB records, and overlay data. Certificate-table presence is metadata only; SigLens does not claim that the signer or trust chain was verified.
siglens gui
siglens gui C:\Samples\sample.exe
.\scripts\Build.ps1
.\dist\SigLens.exe --help
The build includes engine configuration templates and the report schema under
dist\.
Every Ghidra location carries a classification, confidence value when available, and provenance.
| Classification | Meaning | Evidentiary strength |
|---|---|---|
EXACT_MATCH | Exact offset emitted by YARA | Exact |
NATIVE_ENGINE_OFFSET | Offset emitted by a configured engine adapter | Native to that engine |
INFERRED_BOUNDARY | Reproducible transition bounded by prefix measurements | Experimental |
CANDIDATE_REGION | Detected or structurally relevant region | Region-level |
CONTEXT_DEPENDENT | Measurements do not support one responsible location | Indeterminate |
Prefix narrowing records repeated verdicts and controlled checkpoints. If the
same prefix produces conflicting results, or a shorter prefix is detected while
a longer prefix is clean, SigLens reports CONTEXT_DEPENDENT rather than a
single inferred boundary.
Generate an analysis report, verify it against the exact artifact, and export review locations:
siglens scan C:\Samples\sample.exe --yara .\rules --engines .\engines.json
siglens verify-report .\reports\sample.json `
--artifact C:\Samples\sample.exe
siglens ghidra-offsets C:\Samples\sample.exe .\reports\sample.json `
--output .\reports\sample-ghidra.csv `
--script .\reports\ImportSigLens.py