Is xnafx40_redist.msi safe?
Microsoft-signed XNA redistributable installer with zero engine detections and strong historical clean record.
Zero of 75 engines flagged the file. It is signed by Microsoft Corporation, matches a trusted publisher, and appears in the NSRL reference database. Four of five similar Microsoft-signed installers were previously rated safe by our analysis.
e6c41d692ebcba854d…96b8bab01c25e7Recommended next actions
Before installing
Install it only when it came from the developer's official site or an official app store.
If you already installed it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
Zero of 75 engines flagged the file. It is signed by Microsoft Corporation, matches a trusted publisher, and appears in the NSRL reference database. Four of five similar Microsoft-signed installers were previously rated safe by our analysis.
The file is a 2010-era Microsoft XNA Framework redistributable MSI. All 75 engines returned clean results, including 16 tier-1 engines. The certificate is verified and belongs to Microsoft, a curated trusted publisher. The sample is classified as common_old with nearly 63 000 prior submissions, and external intelligence confirms it exists in the NSRL clean reference set. While sandbox heuristics noted process and network activity, these are expected behaviours for a legitimate Windows Installer redistributable. The single dissenting similar-hash record involved a different file type and does not alter the overall evidence.
What We Detected
75 antivirus engines scanned the MSI; none returned a malicious or suspicious result. The binary carries a valid Microsoft Corporation code-signing certificate issued in 2010 and matches our trusted-publisher list. External intelligence shows the hash exists in the NSRL modern reference database under the product name 'Terraria' (XNA redistributable component).
Threat Behavior
Sandbox execution produced typical MSI installer activity: extraction of DirectX setup files, registry writes, and outbound connections to Microsoft content-delivery endpoints. The six flagged MITRE techniques (T1055, T1485, T1486, T1543.003, T1548, T1562.001) map to expected installer operations such as service registration and file replacement, not attacker tradecraft.
What To Do Now
The file can be executed or distributed without elevated security concern. Keep Windows Defender and other endpoint protection enabled; no action is required.
Where this verdict could be wrong1 caveat
- One similar hash (44422e6936dc…) was previously marked malicious under ai_unavailable:circl_known_malicious despite same signer — but that file was d3dcompiler_47.dll, not an installer, and the current sample has no such CIRCL malicious flag.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Microsoft Corporation code signature verified
- Zero detections across 75 engines
- Present in NSRL clean reference database
- 4 of 5 similar Microsoft-signed installers previously rated safe
Treat the file as safe; retain existing endpoint protection and allow normal use.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial18 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete3 signature or behavior rules matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 29MITRE ATT&CK techniques
- 15spawned processes
- 18network contacts
- 40filesystem & mutex artifacts
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
xnafx40_redist.msi
e6c41d692ebcba854dad4b1c52bb7ddd05926bad3105595d6596b8bab01c25e7
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\xnafx40_redist.msi" /qb ACCEPTEULA=1 LicenseAccepted=1
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\services.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
ngen.log
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.log
04Isolated runtime analysis - Written fileObserved
~DFE268FFEAADE4CA4A.TMP
C:\Windows\Temp\~DFE268FFEAADE4CA4A.TMP
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
8.8.8.8
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
92.223.96.6
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- 8.8.8.8
- 92.223.96.6
- 23.215.0.7
- 104.97.85.29
- 23.205.106.153
- 23.218.217.153
- 23.205.106.173
- 208.89.72.69
- 23.205.106.168
- 208.89.72.97
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.log
- C:\Windows\Temp\~DFE268FFEAADE4CA4A.TMP
- C:\Windows\Temp\~DFA628B6689304E987.TMP
- C:\Windows\Temp\~DFFD2211DC2A855AFA.TMP
- C:\Windows\Temp\~DFF1B8A410DEA02975.TMP
- C:\Config.Msi\CMP39E7.tmp
- C:\Config.Msi
- C:\Windows\Installer\11d0b.msi
- C:\Config.Msi\CMP89CC.tmp
- C:\Config.Msi\CMP93BF.tmp
- Global\_MSIExecute
- DirectX Setup
- DSETUP DLL Mutex
- ***DirectXSetupA***
- \Sessions\1\BaseNamedObjects\Global\_MSIExecute
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 7a2f1f07d5b690c1ae80…08c78eNever scannednever seen before
- 8978aa8bdb1e411f7b61…02c26fNever scannednever seen before
- 40a83ea098670844dd84…31eaabNever scannednever seen before
- 8118b1dc3d9536f5fa15…c784c0Never scannednever seen before
- 948d82e57f41947dcb75…4c5500Never scannednever seen before
- 5097a6810a29c8034ca7…7ab2c5Never scannednever seen before
- de0096f72710e1059666…4a66ceNever scannednever seen before
- 39942189cd2a036eabd1…91a91dNever scannednever seen before
- a49c723a698da783e727…ed99adNever scannednever seen before
- 288c701bdedf1d45c63d…970ba3Never scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 3rule hits recorded
- 0 / 75engines flagged
- 3,684sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 75 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash appears in a known-software reference database.
Verdict inputView chapterProvenanceObservedSourceReference software databaseObserved at - 03
The hash has a long, established submission history across 3,684 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 04
Scanned file: xnafx40_redist.msi — e6c41d692ebcba854dad4b1c52bb7ddd05926bad3105595d6596b8bab01c25e7
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\xnafx40_redist.msi" /qb ACCEPTEULA=1 LicenseAccepted=1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\services.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: ngen.log — C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.log
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: ~DFE268FFEAADE4CA4A.TMP — C:\Windows\Temp\~DFE268FFEAADE4CA4A.TMP
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 8.8.8.8 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 92.223.96.6 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
One or more independent reference databases matched this hash.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
EvidenceC:\Windows\system32\DllHost.exe /Processid:{F32D97DF-E3E5-4CB9-9E3E-0EB5B4E49801}Sandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.
EvidenceC:\Windows\system32\lsass.exeThe sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence92.223.96.6 · 23.215.0.7 · 104.97.85.29
0 of 75 engines flagged this file
View all 75 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Fingerprint and provenance
- File name
- xnafx40_redist.msi
- Format
- Windows Installer
- Code signing
- Signature valid: Microsoft Corporation
- Size
- 6.7 MB
- Last analyzed
- Sep 6, 2026, 6:49 AM UTC
e6c41d692ebcba854dad4b1c52bb7ddd05926bad3105595d6596b8bab01c25e7Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Install it only when it came from the developer's official site or an official app store.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is xnafx40_redist.msi safe?
What is xnafx40_redist.msi?
How many antivirus engines detected xnafx40_redist.msi?
Is xnafx40_redist.msi digitally signed?
What is the SHA-256 hash of xnafx40_redist.msi?
Is it safe to install xnafx40_redist.msi?
How up to date is this analysis of xnafx40_redist.msi?
Community
Member reviews and reports for this exact file hash.