Is WinPixEventRuntime.dll safe?
No antivirus engine detected this established Microsoft-signed DLL, and its prevalence, signer history, and related-file results strongly support legitimate software.
All 74 antivirus engines left this Microsoft-signed DLL unflagged, including 17 tier-1 engines. It has circulated since 2019, appears across 590 sources, and matches a signer with 21 of 22 historical samples assessed as benign; the isolated T1055 mapping does not establish harmful intent.
0b71e83dbe737c51ab…76fc4920a66a65Recommended 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.
All 74 antivirus engines left this Microsoft-signed DLL unflagged, including 17 tier-1 engines. It has circulated since 2019, appears across 590 sources, and matches a signer with 21 of 22 historical samples assessed as benign; the isolated T1055 mapping does not establish harmful intent.
The sample received no malicious or suspicious detections from 74 antivirus engines, with all 17 reporting tier-1 engines finding nothing actionable. Its digital signature verifies as Microsoft Corporation and matches the curated Microsoft publisher record. It is also well established, with 674 submissions from 590 sources since June 2019, while five signer-matched historical files received benign assessments. One sandbox mapped activity to T1055, but it did not issue a malicious sandbox verdict, and none of ten inspected child files was identified as malicious. No complete contacted-host reputation result was saved, but the available sandbox record contains no network contacts.
What We Detected
No antivirus engine flagged the DLL: 0 of 74 reported it as malicious or suspicious, and all 17 reporting tier-1 engines were clear. The file carries a verified Microsoft Corporation signature, with signing.trustedPublisher.matched=true. It is established software observed since 2019 across 590 sources and 674 submissions.
Threat Behavior
One completed sandbox run mapped activity to MITRE T1055, which can describe process injection. That mapping alone does not establish malicious intent, particularly because the sandbox issued no malicious verdict, eight other mapped techniques were benign-common, and no persistence or registry changes were recorded. Ten child artifacts were inspected without any malicious child finding. No complete contacted-host reputation cross-check is available, although this run recorded no contacted domains, IP addresses, or URLs.
What To Do Now
The evidence is consistent with a legitimate Microsoft runtime component. Keep endpoint protection enabled and obtain the DLL through the application or vendor's normal installation channel; investigate further only if its signature fails verification on the local system or it appeared in an unexpected location.
Where this verdict could be wrong3 caveats
- behaviour.offensiveTechniques includes T1055, mapped from one sandbox run; the mapping indicates possible process injection but no sandbox produced a malicious verdict.
- signing.signerStats includes 1/22 historically malicious samples, so the publisher signature is strong but not absolute evidence.
- contactedHosts=null means no saved host-reputation cross-check is available, although the sandbox recorded no contacted domains, IPs, or URLs.
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 of 74 antivirus engines detected the file.
- Verified Microsoft Corporation signature and trusted-publisher match.
- All 17 reporting tier-1 engines were clear.
- Established prevalence: 590 sources and 674 submissions since 2019.
- Five of five signer-matched historical files received safe verdicts.
- One sandbox run mapped activity to MITRE T1055.
- The signer history contains 1 malicious assessment among 22 samples.
- No complete contacted-host reputation cross-check was saved.
Keep endpoint protection enabled and use the DLL only as supplied by its legitimate application or vendor channel. Recheck the local signature if the file resides in an unexpected directory or arrived separately.
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
- 9MITRE 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
WinPixEventRuntime.dll
0b71e83dbe737c51ab7345541a4914790962e9a9466b74c4c076fc4920a66a65
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 2924 -s 536
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
19870606-d630-419b-bb15-d4ec3994ef21
C:\ProgramData\Microsoft\Windows\WER\Temp\19870606-d630-419b-bb15-d4ec3994ef21
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\19870606-d630-419b-bb15-d4ec3994ef21
- C:\ProgramData\Microsoft\Windows\WER\ReportQueue
- C:\ProgramData\Microsoft\Windows\WER\Temp\2c41ca51-7c61-4c3e-8589-56b3abd2ce80
- C:\ProgramData\Microsoft\Windows\WER\ReportArchive
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER3DDA.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER4349.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER44B2.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER3DDA.tmp.dmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER4349.tmp.WERInternalMetadata.xml
- Local\WERReportingForProcess2924
- Global\AmiProviderMutex_InventoryApplicationFile
- Global\7e4dae0e-a878-43f7-9cea-50fca89f12c1
- \Sessions\1\BaseNamedObjects\Local\WERReportingForProcess6660
- \Sessions\1\BaseNamedObjects\Global\73ff7650-9f59-4e46-bf50-6682747cdcea
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- e033b4591ed88cf7d78d…53a256Never scannednever seen before
- 5b859911676dd4ccc6e1…5dedb6Never scannednever seen before
- a6fd73d80b9f07ce0280…7616c6Never scannednever seen before
- 24808f94bc6b596fc45e…ba02adNever scannednever seen before
- 0dc7fd1aa9cf1906cba1…4957daNever scannednever seen before
- 80cfc5917fc5b6785116…6b78a3Never scannednever seen before
- b0b1804a1da23d6fffe4…6ca385Never scannednever seen before
- 7506fcde5771567a4395…1344edNever scannednever seen before
- 6a54f2defeeb35851862…895e68Never scannednever seen before
- da0f57d1aad4d30050fc…1ae020Never 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
- 590sources 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 590 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 04
Scanned file: WinPixEventRuntime.dll — 0b71e83dbe737c51ab7345541a4914790962e9a9466b74c4c076fc4920a66a65
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 2924 -s 536
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Temp — C:\ProgramData\Microsoft\Windows\WER\Temp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: 19870606-d630-419b-bb15-d4ec3994ef21 — C:\ProgramData\Microsoft\Windows\WER\Temp\19870606-d630-419b-bb15-d4ec3994ef21
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:\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
- WinPixEventRuntime.dll
- Format
- Win32 DLL
- Code signing
- Signature valid: Microsoft Corporation
- Size
- 34.1 KB
- Last analyzed
- Sep 23, 2026, 5:25 AM UTC
0b71e83dbe737c51ab7345541a4914790962e9a9466b74c4c076fc4920a66a65Safety & 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 WinPixEventRuntime.dll safe?
What is WinPixEventRuntime.dll?
How many antivirus engines detected WinPixEventRuntime.dll?
Is WinPixEventRuntime.dll digitally signed?
What is the SHA-256 hash of WinPixEventRuntime.dll?
Is it safe to use WinPixEventRuntime.dll?
How up to date is this analysis of WinPixEventRuntime.dll?
Community
Member reviews and reports for this exact file hash.