Is this MSI safe? A triage checklist
A practical, static checklist for deciding whether a Windows Installer package is worth trusting — signature, custom actions, payload and reach.
No static check proves a package is safe — only that it does, or doesn't, do the things that tend to matter. Here is the order I read an unknown MSI in. Every step is static: nothing runs.
1. Identity
Read the Summary Information and the
Property table. Does the ProductName, Manufacturer and
ProductVersion match what you were told this is? Note the ProductCode and
UpgradeCode — you can look them up or compare them across samples.
2. Signature
Is there a digital signature? An unsigned installer isn't automatically bad, but a signed one tells you who built it — read the signer certificate's subject. (Offline, the chain and revocation aren't validated; trust still needs a trust store.)
3. Custom actions
The decisive step. Read every custom action:
- Does it run an EXE, load a DLL, or execute JScript/VBScript?
- Is anything deferred and no-impersonate (runs as SYSTEM)?
- Are there nested installs?
- Where does each action's code come from — the
Binarytable, a file, inline?
4. Payload and reach
- List the embedded cabinets and the
Binarytable: what files and payloads does the package carry, and what are they (EXE, DLL, script)? - Scan the
Registry,ServiceInstall,ShortcutandEnvironmenttables: does it install a service, change startup, or alter the environment? - Check strings and property values for external URLs.
5. Decide
A clean installer: identity matches, signed by a plausible vendor, no code-running custom actions beyond the vendor's own, payload consistent with the product. A package that runs an unsigned EXE as SYSTEM, reaches a URL, and installs a service deserves a closer look — in a lab, not on a fleet.
MSI Parser runs this whole checklist in your browser and surfaces the findings as plain-language indicators. Drop a package and read it — nothing leaves the tab.