Is Qt5Core.dll safe?
No antivirus engine detected this established, validly signed CD PROJEKT DLL, and its runtime and structural evidence revealed no corroborating threat activity.
All 74 antivirus engines returned no detection, including 17 tier-1 engines. The DLL is validly signed by CD PROJEKT S.A., is broadly established across 365 sources, and produced no offensive techniques or malicious sandbox assessment during one completed run.
5f211f05695e1e0d26…a947ab001ec0daRecommended 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 returned no detection, including 17 tier-1 engines. The DLL is validly signed by CD PROJEKT S.A., is broadly established across 365 sources, and produced no offensive techniques or malicious sandbox assessment during one completed run.
The antivirus result is uniformly favorable: 0 of 74 engines flagged the DLL, and all 17 reporting tier-1 engines were silent. Its signature verifies to CD PROJEKT S.A., with no conflict between the claimed brand and signer. The sample is established across 365 sources and 404 submissions, which reduces concern that it is an isolated impersonation. One completed sandbox run recorded no offensive techniques, malicious assessment, persistence indicators, dropped hashes, or network contacts. Static PE analysis found no packing, high-entropy code, or suspicious section, while five previous signer-matched files received clean assessments.
What We Detected
None of 74 antivirus engines flagged the DLL, including all 17 tier-1 engines. The file carries a verified signature from CD PROJEKT S.A., and no publisher-brand mismatch was detected. It is also well established, appearing across 365 sources and 404 submissions.
Threat Behavior
One completed sandbox run produced no offensive techniques, malicious sandbox assessment, persistence indicators, dropped file hashes, or no complete contacted-host reputation result was available-common environmental and loading activity. Static PE inspection found no packer, high-entropy code, or suspicious section.
What To Do Now
The evidence is consistent with a legitimate Qt runtime component distributed with CD PROJEKT software. Keep endpoint protection enabled and obtain or restore the DLL through the original game client, publisher, or trusted software distribution channel if its source is uncertain.
Where this verdict could be wrong3 caveats
- signing.signerStats.totalSamples=1 provides little standalone history, although five additional signer-matched prior verdicts are consistently safe.
- contactedHosts=null, so no completed host-reputation cross-check is available; the sandbox recorded no contacted domains, IPs, or URLs.
- The file tags include 'detect-debug-environment' and 'corrupt', but no engine detection, offensive technique, packing indicator, or malicious sandbox verdict corroborates them.
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 detected a threat.
- 17/17 tier-1 engines reported no detection.
- Verified signature from CD PROJEKT S.A.
- 365 unique sources and 404 submissions indicate established prevalence.
- 5/5 prior signer-matched files received safe verdicts.
- File tags include detect-debug-environment and corrupt, without corroborating malicious evidence.
- The stored signer statistics cover only 1 sample.
- No complete contacted-host reputation result is available.
Use the DLL normally when it came with legitimate CD PROJEKT software. If its origin is unknown, replace it through the official game client or publisher while keeping 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
CompleteRule evaluation completed with no recorded matches.
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
- 17MITRE ATT&CK techniques
- 8spawned processes
- 0network contacts
- 2filesystem & 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
Qt5Core.dll
5f211f05695e1e0d26c0eaeab2d4774ee43a131d108e7ec2e9a947ab001ec0da
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\Desktop\Qt5Core.dll",#1
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\System32\loaddll64.exe loaddll64.exe "C:\Users\user\Desktop\Qt5Core.dll"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Connect
\Device\ConDrv\\Connect
04Isolated runtime analysis
4 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.
- \Device\ConDrv\\Connect
- \Sessions\1\BaseNamedObjects\Local\SessionImmersiveColorMutex
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 0rule hits recorded
- 0 / 74engines flagged
- 365sources 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 365 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
The file has a valid code signature from CD PROJEKT S.A..
ProvenanceObservedSourceCode-signing metadataObserved at - 04
Scanned file: Qt5Core.dll — 5f211f05695e1e0d26c0eaeab2d4774ee43a131d108e7ec2e9a947ab001ec0da
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\Desktop\Qt5Core.dll",#1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\System32\loaddll64.exe loaddll64.exe "C:\Users\user\Desktop\Qt5Core.dll"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Connect — \Device\ConDrv\\Connect
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.
YARA rules
No matchesThe rule pass completed without a saved public match.
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
- Qt5Core.dll
- Format
- Win32 DLL
- Code signing
- Signature valid: CD PROJEKT S.A.
- Size
- 7.2 MB
- Last analyzed
- Sep 23, 2026, 4:45 AM UTC
5f211f05695e1e0d26c0eaeab2d4774ee43a131d108e7ec2e9a947ab001ec0daSafety & 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 Qt5Core.dll safe?
What is Qt5Core.dll?
How many antivirus engines detected Qt5Core.dll?
Is Qt5Core.dll digitally signed?
What is the SHA-256 hash of Qt5Core.dll?
Is it safe to use Qt5Core.dll?
How up to date is this analysis of Qt5Core.dll?
Community
Member reviews and reports for this exact file hash.