Is vcruntime140.dll safe?
No antivirus engine detected this established runtime DLL, while its broad prevalence and historical signer matches outweigh uncorroborated process-injection telemetry.
None of 74 antivirus engines flagged the DLL, including all 17 tier-1 engines, and the sample has circulated for nearly five years. The unverified signature and sandbox mappings to process injection and defense impairment merit caution, but no malicious sandbox outcome, child file, family consensus, or external-intelligence match corroborates them.
0b797e8c953485f131…20f9200e837e2cRecommended next actions
Before using
Use it only as part of software obtained from the developer's official site or another source you independently trust.
If you already used 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.
None of 74 antivirus engines flagged the DLL, including all 17 tier-1 engines, and the sample has circulated for nearly five years. The unverified signature and sandbox mappings to process injection and defense impairment merit caution, but no malicious sandbox outcome, child file, family consensus, or external-intelligence match corroborates them.
The strongest evidence is unanimous antivirus silence: 0 of 74 engines flagged the file, including 17 tier-1 engines. It is also established rather than novel, with 110 sources and 143 submissions over 1,817 days. Five signer-matched historical samples received benign assessments, and 21 of 22 samples associated with the signer have similar history. The claimed Microsoft signature is not verified, so the signer name provides only contextual support rather than authentication. One sandbox mapped activity to T1055 and T1562.001, but it produced no malicious verdict, and none of the ten inspected child hashes was identified as malicious. No complete contacted-host reputation result is available, although the observed run recorded no network contacts.
What We Detected
None of 74 antivirus engines reported a malicious or suspicious result. All 17 tier-1 engines, including Avast, BitDefender, ESET-NOD32, and Kaspersky, reported no detection. The sample is well established, with 110 distinct sources and 143 submissions since September 2021, and five prior signer-matched files received benign assessments.
Threat Behavior
One sandbox run mapped activity to MITRE T1055 and T1562.001, including rundll32 loading a DLL from a desktop attachment path. These are meaningful risk indicators, but the run produced no malicious sandbox verdict, no persistence indicators, and no observed network contacts. Ten child hashes were inspected and none was identified as malicious, although their individual classifications remain unknown. The contacted-host reputation block was not available, so no complete host-reputation conclusion can be made.
What To Do Now
The file is consistent with a commonly distributed Visual C++ runtime component, but its signature was not verified. Prefer a copy obtained directly through Microsoft software or a trusted application's installer, compare its hash with the vendor-provided package where possible, and keep endpoint protection enabled.
Where this verdict could be wrong4 caveats
- The signature is not verified: signing.verified=null and signing.trustedPublisher.matched=false, so the 'Microsoft Corporation' signer name is not independently trustworthy.
- One completed sandbox mapped activity to T1055 and T1562.001, including rundll32 loading a DLL from a desktop attachment path; these techniques can be abused despite the lack of a malicious sandbox verdict.
- The file carries the 'invalid-signature' tag, which conflicts with treating the signer identity as validated.
- contactedHosts=null, although the sandbox recorded no network contacts; consequently, no complete host-reputation assessment is available.
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 detection
- All 17 tier-1 engines reported no detection
- Common sample with 110 sources and 143 submissions
- 5/5 signer-matched historical verdicts were safe
- No malicious sandbox verdict or malicious dropped child
- signing.verified=null despite the 'Microsoft Corporation' signer claim
- file.tags includes 'invalid-signature'
- Sandbox telemetry mapped activity to MITRE T1055
- Sandbox telemetry mapped activity to MITRE T1562.001
- rundll32 loaded a DLL from a desktop attachment path
- contactedHosts=null, leaving host-reputation coverage unavailable
Use the DLL if it came from Microsoft or a trusted application's installer; otherwise replace it with a vendor-supplied copy. Keep antivirus and endpoint protection enabled.
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
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
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
- 12MITRE ATT&CK techniques
- 2spawned processes
- 0network 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
vcruntime140.dll
0b797e8c953485f131a3968f1b16f4ef053fe235e1ef20e59620f9200e837e2c
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\Desktop\attachment.dll",#1
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\WerFault.exe -u -p 728 -s 456
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Temp
C:\ProgramData\Microsoft\Windows\WER\Temp
04Isolated runtime analysis - Written fileObserved
593ad0d4-0e29-43b4-8bbf-d2ad686b7968
C:\ProgramData\Microsoft\Windows\WER\Temp\593ad0d4-0e29-43b4-8bbf-d2ad686b7968
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
5 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.
- C:\ProgramData\Microsoft\Windows\WER\Temp
- C:\ProgramData\Microsoft\Windows\WER\Temp\593ad0d4-0e29-43b4-8bbf-d2ad686b7968
- C:\ProgramData\Microsoft\Windows\WER\ReportQueue
- C:\ProgramData\Microsoft\Windows\WER\Temp\31fe60b0-6eeb-494f-a221-ec0ad41093fc
- C:\ProgramData\Microsoft\Windows\WER\ReportArchive
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER422F.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER49C2.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER4BC6.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER422F.tmp.dmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER49C2.tmp.WERInternalMetadata.xml
- Local\WERReportingForProcess728
- Global\AmiProviderMutex_InventoryApplicationFile
- Global\93f95042-ed55-44a7-b125-206e6155f52e
- \Sessions\1\BaseNamedObjects\Local\WERReportingForProcess2568
- \Sessions\1\BaseNamedObjects\Global\35460438-f689-4869-9e83-a78fb90da311
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 123cfc16ab795bbac0be…3446b9Never scannednever seen before
- e4da1750fddb9e701332…27f021Never scannednever seen before
- 1d3e2450b3e49c2e6d73…9a9b18Never scannednever seen before
- 2d25d3feb6640b339de1…0287b6Never scannednever seen before
- be80be768d38be253994…297288Never scannednever seen before
- 31818b137c45ba9363fa…1669adNever scannednever seen before
- 5db6360a75f091d3ccd3…39119fNever scannednever seen before
- b825afb48b07b07a00b0…3b5e73Never scannednever seen before
- 801b681a935dbc02eef7…b3b3eaNever scannednever seen before
- 516e571f911b3f502bb7…9cce9fNever 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 / 74engines flagged
- 110sources 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 has a long, established submission history across 110 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 04
Scanned file: vcruntime140.dll — 0b797e8c953485f131a3968f1b16f4ef053fe235e1ef20e59620f9200e837e2c
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\Desktop\attachment.dll",#1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\WerFault.exe -u -p 728 -s 456
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Temp — C:\ProgramData\Microsoft\Windows\WER\Temp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: 593ad0d4-0e29-43b4-8bbf-d2ad686b7968 — C:\ProgramData\Microsoft\Windows\WER\Temp\593ad0d4-0e29-43b4-8bbf-d2ad686b7968
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for 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:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\Desktop\attachment.dll",#1
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
- vcruntime140.dll
- Format
- Win32 DLL
- Code signing
- Signature not verified: Microsoft Corporation
- Size
- 91.9 KB
- Last analyzed
- Sep 20, 2026, 2:05 PM UTC
0b797e8c953485f131a3968f1b16f4ef053fe235e1ef20e59620f9200e837e2cSafety & 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
Use it only as part of software obtained 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 vcruntime140.dll safe?
What is vcruntime140.dll?
How many antivirus engines detected vcruntime140.dll?
Is vcruntime140.dll digitally signed?
What is the SHA-256 hash of vcruntime140.dll?
Is it safe to use vcruntime140.dll?
How up to date is this analysis of vcruntime140.dll?
Community
Member reviews and reports for this exact file hash.