Is VC_redist.x64.exe safe?
No antivirus engine detected this verified Microsoft-signed redistributable, and its extensive prevalence and signer history strongly support legitimate installer activity.
All 74 antivirus engines avoided a malware or suspicious detection, including 14 tier-1 engines that reported no detection. The verified Microsoft signature, broad long-term prevalence, five consistent signer-based precedents, and absence of a malicious sandbox verdict outweigh the installer-related behavioral alerts.
b6c82087a2c443db85…0358066253de52Recommended 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.
All 74 antivirus engines avoided a malware or suspicious detection, including 14 tier-1 engines that reported no detection. The verified Microsoft signature, broad long-term prevalence, five consistent signer-based precedents, and absence of a malicious sandbox verdict outweigh the installer-related behavioral alerts.
The file carries a verified Microsoft Corporation signature that matches a curated trusted publisher. None of 74 antivirus engines flagged it, and 14 tier-1 engines explicitly reported no detection. It has accumulated 55,478 submissions from 3,709 sources since 2020, which is consistent with widely distributed Microsoft runtime software. One sandbox mapped activity to T1055, T1134, and T1543.003, but produced no malicious verdict, and none of 10 inspected children was identified as malicious. Direct-IP traffic remains a limitation because no complete host-reputation result is available, yet there is no independent detection or threat-intelligence corroboration for command-and-control activity.
What We Detected
No malware or suspicious detection was reported by 74 antivirus engines. The executable is signed by Microsoft Corporation, the signature is verified, and the publisher matches the curated trusted-publisher record. It is also well established, with 55,478 submissions from 3,709 sources since January 2020.
Threat Behavior
One completed sandbox run mapped activity to T1055, T1134, and T1543.003 and recorded direct-IP connections. These mappings can be concerning in isolation, but the sandbox issued no malicious verdict and the evidence does not establish hostile intent. Ten dropped children were inspected without identifying a malicious child, although their individual verdicts remain unknown. No complete host-reputation result is available for the observed IP contacts.
What To Do Now
If this file came from Microsoft or a trusted software installer, it is consistent with a legitimate Visual C++ redistributable. Keep endpoint protection enabled and verify the SHA-256 value and digital signature if the file arrived from an unfamiliar download source.
Where this verdict could be wrong3 caveats
- behaviour.offensiveTechniques includes T1055, T1134, and T1543.003, although the sandbox issued no malicious verdict.
- MalwareTips.Synth.DirectIpC2 fired for direct-IP traffic, but contactedHosts=null means no complete host-reputation result is available.
- droppedChildren inspected 10 children without identifying a malicious child, but all 10 individual child verdicts remain unknown.
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/74 antivirus engines reported a malicious or suspicious result.
- Verified Microsoft Corporation digital signature.
- Curated trusted-publisher match for Microsoft.
- 21/22 historical signer samples were safe.
- 55,478 submissions from 3,709 sources since 2020.
- Runtime evidence mapped activity to MITRE T1055, T1134, and T1543.003.
- Direct-IP connections were observed, but their reputation was not completely checked.
- The 10 inspected child files have unknown individual verdicts.
Use the file if its source and verified Microsoft signature are intact. Keep endpoint protection enabled, and obtain a fresh copy from Microsoft if the download origin is uncertain.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial20 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete2 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
- 24MITRE ATT&CK techniques
- 15spawned processes
- 20network contacts
- 37filesystem & 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
VC_redist.x64.exe
b6c82087a2c443db859fdbeaae7f46244d06c3f2a7f71c35e50358066253de52
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\file.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Windows\Temp\{FF56C408-9E27-4A04-AA19-46C406ECF471}\.cr\file.exe" -burn.clean.room="C:\Users\<USER>\Desktop\file.exe" -burn.filehandle.attached=656 -burn.filehandle.self=664
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
file.exe
C:\Windows\Temp\{FF56C408-9E27-4A04-AA19-46C406ECF471}\.cr\file.exe
04Isolated runtime analysis - Written fileObserved
wixstdba.dll
C:\Windows\Temp\{4819AFD0-85E4-4A42-BA57-E88A93B5A3B3}\.ba\wixstdba.dll
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
a83f:8110:cce1:d301:10:0:0:0
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
23.59.190.203
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.
- a83f:8110:cce1:d301:10:0:0:0
- 23.59.190.203
- 23.216.147.64
- 52.251.79.25
- 192.168.0.31
- 13.107.4.50
- a83f:8110:dd62:d801:8ad2:a7a8:dd62:d801
- 23.216.147.76
- 20.99.132.105
- 131.253.33.203
- C:\Windows\Temp\{FF56C408-9E27-4A04-AA19-46C406ECF471}\.cr\file.exe
- C:\Windows\Temp\{4819AFD0-85E4-4A42-BA57-E88A93B5A3B3}\.ba\wixstdba.dll
- C:\Windows\Temp\{4819AFD0-85E4-4A42-BA57-E88A93B5A3B3}\.ba\thm.xml
- C:\Windows\Temp\{4819AFD0-85E4-4A42-BA57-E88A93B5A3B3}\.ba\thm.wxl
- C:\Windows\Temp\{4819AFD0-85E4-4A42-BA57-E88A93B5A3B3}\.ba\logo.png
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER13F1.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER13E1.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER14AD.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER14AC.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER14EC.tmp.txt
- 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.
- 82c3e3423e48bafcdd72…43b022Never scannednever seen before
- 2ac8b7c19a5189662de3…39f9caNever scannednever seen before
- f13bae0ec08c91b4a315…4d6916Never scannednever seen before
- 70400f181d00e1769774…4ef4ceNever scannednever seen before
- 32585b93e69272b6d42d…d78c49Never scannednever seen before
- 335a256d4779ec5dcf28…2744efNever scannednever seen before
- ad7608b87a7135f408ab…ae90b2Never scannednever seen before
- e95ca64c326a0ef7ef3c…44d0e0Never scannednever seen before
- 8cb5eb330aa07accd6d1…5af617Never scannednever seen before
- a3f745c01dea84ce746b…33be22Never 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.
- 2rule hits recorded
- 0 / 74engines flagged
- 3,709sources 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 74 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,709 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 04
Scanned file: VC_redist.x64.exe — b6c82087a2c443db859fdbeaae7f46244d06c3f2a7f71c35e50358066253de52
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\file.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Windows\Temp\{FF56C408-9E27-4A04-AA19-46C406ECF471}\.cr\file.exe" -burn.clean.room="C:\Users\<USER>\Desktop\file.exe" -burn.filehandle.attached=656 -burn.filehandle.self=664
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: file.exe — C:\Windows\Temp\{FF56C408-9E27-4A04-AA19-46C406ECF471}\.cr\file.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: wixstdba.dll — C:\Windows\Temp\{4819AFD0-85E4-4A42-BA57-E88A93B5A3B3}\.ba\wixstdba.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: a83f:8110:cce1:d301:10:0:0:0 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 23.59.190.203 — 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.
Evidence"C:\Users\<USER>\Desktop\file.exe"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.
Evidencea83f:8110:cce1:d301:10:0:0:0 · 23.59.190.203 · 23.216.147.64
0 of 74 engines flagged this file
View all 74 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
- VC_redist.x64.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: Microsoft Corporation
- Size
- 14.3 MB
- Last analyzed
- Sep 23, 2026, 8:54 PM UTC
b6c82087a2c443db859fdbeaae7f46244d06c3f2a7f71c35e50358066253de52Safety & 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 VC_redist.x64.exe safe?
What is VC_redist.x64.exe?
How many antivirus engines detected VC_redist.x64.exe?
Is VC_redist.x64.exe digitally signed?
What is the SHA-256 hash of VC_redist.x64.exe?
Is it safe to run VC_redist.x64.exe?
How up to date is this analysis of VC_redist.x64.exe?
Community
Member reviews and reports for this exact file hash.