LOCAL STATIC FILE ANALYSIS

Know what’s hiding
inside the document.

Upload an Office document, Windows installer, ZIP archive, JSON file, or JavaScript source. We’ll map static indicators into a report you can actually read.

Drop an Office, MSI, ZIP, JSON, or JS file here or click to browse your computer

DOCM · XLSM · PPTM · MSI · ZIP · JSON · JS Up to 100 MB

Also run local ThreatCheck (optional; may take up to 60 seconds) ThreatCheck engine

Never executedYour document is only parsed

App uploads removedExternal tools may retain artifacts

Bounded inspectionOffice, MSI, ZIP, and JSON analysis

ANALYSIS COMPLETE

DOC

SHA-256

Macro modules0

Auto-exec triggers0

Suspicious items0

Indicators (IOCs)0

Findings

Severity	Type	Keyword	What it means

Extracted modules

ThreatCheck · AMSI

Flagged-byte context

Package identity & checks

Product

Package signature

PrevalenceNot checkedLocal analysis only. No hash was sent to a reputation service.

Package signing and installed-file signing are separate checks. File-level signatures and SHA-256 hashes require extracting payload bytes; they are not inferred from the MSI database.

Packaged files

Names, sizes, and probable destinations come from MSI tables. Runtime properties and transforms can change the final paths.

File	Size	Probable destination	File signature

Registry changes

No registry rows declared.

Hive	Key	Name	Value

Embedded streams & media

Binary-table entries are inventoried, not extracted or code-scanned in this version.

Contained-file inspection

Community

Static analysis:

Know what’s hidinginside the document.