Is dotNetFx40_Full_x86_x64.exe safe?
Widely submitted .NET Framework installer with zero engine detections and an NSRL reference entry.
Zero of 75 engines flagged the file. The sample matches a known .NET Framework redistributable that has been submitted by over 2300 sources since 2011 and carries an NSRL reference. No malicious children, sandbox verdicts, or tier-1 detections are present.
1a1e67809c73cec352…5f8575f1acaf10Recommended next actions
Before running
Run it only when it came from the developer's official site or another source you independently trust.
If you already ran 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. The sample matches a known .NET Framework redistributable that has been submitted by over 2300 sources since 2011 and carries an NSRL reference. No malicious children, sandbox verdicts, or tier-1 detections are present.
The file is an unsigned Win32 EXE named dotNetFx40_Full_x86_x64.exe that has existed in the wild for 5567 days and carries a reputation score of 40. All 75 reporting engines returned clean results, including 17 tier-1 engines. External intelligence shows an NSRL hit with no known-malicious flag. Sandbox execution produced only ambient techniques and no malicious verdict. Although the sample contacted 19 direct IPs, the heuristic rule itself notes that such traffic occurs in legitimate installers and requires host-reputation correlation, which is unavailable because contactedHosts is null.
What We Detected
75 engines scanned the sample; none returned a malicious or suspicious result. The file is unsigned and contains no code-signing certificate. Sandbox analysis recorded nine ambient MITRE techniques and wrote several temporary files, but produced no malicious verdict and no malicious dropped children.
Threat Behavior
No offensive techniques, persistence mechanisms, or C2 indicators were observed. The single triggered heuristic (DirectIpC2) notes that direct-IP traffic can occur in legitimate installers and must be correlated with host reputation; that correlation is unavailable because the host-reputation check was not completed.
What To Do Now
The file matches the expected profile of the Microsoft .NET Framework 4.0 redistributable. Keep endpoint protection enabled and obtain official installers only from Microsoft’s download center.
Where this verdict could be wrong1 caveat
- contactedHosts=null means host-reputation cross-check was not completed; cannot assert clean network behaviour.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0/75 engines malicious
- common_old prevalence with 2302 submitters
- NSRL reference entry, no known-malicious flag
The evidence supports treating the file as a benign, widely distributed .NET Framework installer; no further action is required beyond obtaining it from official sources.
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
Partial20 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete1 signature or behavior rule 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
- 9MITRE ATT&CK techniques
- 10spawned processes
- 20network contacts
- 36filesystem & 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
dotNetFx40_Full_x86_x64.exe
1a1e67809c73cec352fa6a2cc86aa8d09fb41c1d39db5ca8a75f8575f1acaf10
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\dotNetFx40_Full_x86_x64.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
%SAMPLEPATH%\dotNetFx40_Full_x86_x64.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
dd_dotNetFx40_Full_x86_x64_decompression_log.txt
C:\Users\<USER>\AppData\Local\Temp\dd_dotNetFx40_Full_x86_x64_decompression_log.txt
04Isolated runtime analysis - Written fileObserved
dd_996E_decompression_log.txt
C:\Documents and Settings\Administrator\Local Settings\Temp\dd_996E_decompression_log.txt
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
204.79.197.203
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
74.125.69.94
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.
- 204.79.197.203
- 74.125.69.94
- 23.216.147.76
- 192.168.0.178
- a83f:8110:766b:c00:1a00:0:5853:4200
- 23.216.147.64
- a83f:8110:ff7f:0:e101:0:0:0
- 20.99.132.105
- 20.99.133.109
- a83f:8110:e5c0:7cff:e5c0:7cff:e5c0:7cff
- C:\Users\<USER>\AppData\Local\Temp\dd_dotNetFx40_Full_x86_x64_decompression_log.txt
- C:\Documents and Settings\Administrator\Local Settings\Temp\dd_996E_decompression_log.txt
- C:\Users\<USER>\AppData\Local\Temp\dd_1a1e67809c73cec352fa6a2cc86aa8d09fb41c1d39db5ca8a75f8575f1acaf10_decompression_log.txt
- C:\077cab0c-9802-4c15-a5fa-c95193d57c5e
- C:\7ef84bab71cfa836c1b668ee0b06ff\
- C:\3bd79fb9eb4c9fd04e1175d4\
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER11BE.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER126A.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER1299.tmp.txt
- C:\Windows\System32\spp\store\2.0\cache\cache.dat
- CTF.LBES.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Compart.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Asm.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Layouts.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.TMD.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 497b80ff87111eab6807…7e3b0dNever scannednever seen before
- e0895f55a91feb54d3b8…805757Never scannednever seen before
- 83b420aea0723ac27cce…1f6e44Never scannednever seen before
- 35e0b370fd3ae087e5b7…3fbfe6Never scannednever seen before
- 82a11b97fc4d497302e5…f1d6acNever scannednever seen before
- 603ea6e6748b810a6bb0…c0acdcNever scannednever seen before
- e2ef7eb50834217ab6d5…07773fNever scannednever seen before
- 97bb3d4337dd00e70f97…4e96c1Never scannednever seen before
- 37496084973d0a8f71cd…871171Never scannednever seen before
- 51064ad74262e7ffcf9d…3ddd5aNever 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.
- 1rule hit recorded
- 0 / 75engines flagged
- 2,302sources 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 2,302 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 04
Scanned file: dotNetFx40_Full_x86_x64.exe — 1a1e67809c73cec352fa6a2cc86aa8d09fb41c1d39db5ca8a75f8575f1acaf10
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\dotNetFx40_Full_x86_x64.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — %SAMPLEPATH%\dotNetFx40_Full_x86_x64.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: dd_dotNetFx40_Full_x86_x64_decompression_log.txt — C:\Users\<USER>\AppData\Local\Temp\dd_dotNetFx40_Full_x86_x64_decompression_log.txt
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: dd_996E_decompression_log.txt — C:\Documents and Settings\Administrator\Local Settings\Temp\dd_996E_decompression_log.txt
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 204.79.197.203 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 74.125.69.94 — 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
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
The 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.
Evidence204.79.197.203 · 74.125.69.94 · 23.216.147.76
0 of 75 engines flagged this file
View all 75 engine results
Section entropy & packers
No high-entropy executable section or known packer signature was detected. Data and resource sections can still have high entropy without indicating packed code.
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
- dotNetFx40_Full_x86_x64.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 1.5 MB
- Last analyzed
- Sep 6, 2026, 6:47 AM UTC
1a1e67809c73cec352fa6a2cc86aa8d09fb41c1d39db5ca8a75f8575f1acaf10Safety & 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
Run it only when it came from the developer's official site or another source you independently trust.
- 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 dotNetFx40_Full_x86_x64.exe safe?
What is dotNetFx40_Full_x86_x64.exe?
How many antivirus engines detected dotNetFx40_Full_x86_x64.exe?
What is the SHA-256 hash of dotNetFx40_Full_x86_x64.exe?
Is it safe to run dotNetFx40_Full_x86_x64.exe?
How up to date is this analysis of dotNetFx40_Full_x86_x64.exe?
Community
Member reviews and reports for this exact file hash.