Is POCO safe?
The verified CD PROJEKT DLL has no detections across 74 engines, established prevalence, and five consistent publisher-matched historical results.
No antivirus engine flagged this verified CD PROJEKT S.A. DLL, including all 17 reporting tier-1 engines. Its established prevalence and five publisher-matched historical results strongly support legitimate commodity software, while the sandbox’s T1055 mapping remains an isolated caution without a malicious runtime conclusion.
019ebd418c64d468fe…13f135365d7411Recommended next actions
Before opening
Open it only when its sender or download source is one you independently trust.
If you already opened 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.
No antivirus engine flagged this verified CD PROJEKT S.A. DLL, including all 17 reporting tier-1 engines. Its established prevalence and five publisher-matched historical results strongly support legitimate commodity software, while the sandbox’s T1055 mapping remains an isolated caution without a malicious runtime conclusion.
The sample received no malicious or suspicious detections from 74 engines, with all 17 reporting tier-1 engines returning no detection. Its signature verifies to CD PROJEKT S.A., and the evidence identifies no publisher-brand conflict. It has circulated for 431 days across 286 sources and 319 submissions, which is inconsistent with a newly distributed payload. Five signer-matched files previously received clean outcomes, providing strong historical corroboration. One sandbox mapped execution to T1055 and T1543.003, but it produced no malicious verdict, persistence indicators, dropped hashes, or network contacts. A complete contacted-host reputation result is unavailable, though no hosts were observed during the saved run.
What We Detected
None of 74 antivirus engines flagged the DLL, and all 17 reporting tier-1 engines returned no detection. The file carries a verified signature from CD PROJEKT S.A., with no detected mismatch between its claimed identity and signer.
Threat Behavior
One completed sandbox run mapped activity to T1055 and T1543.003. These techniques can be security-relevant, but the run produced no malicious sandbox conclusion, persistence indicators, registry changes, dropped file hashes, or observed network contacts. The file is not statically identified as packed, and its code section does not have unusually high entropy.
What To Do Now
The established distribution history and five clean signer-matched results support normal use when the DLL came from an official CD PROJEKT installation or update. If it appeared outside an expected game or application directory, verify the signature and source before loading it, and keep endpoint protection enabled.
Where this verdict could be wrong3 caveats
- triggeredHeuristics[0] maps sandbox activity to T1055 Process Injection, an offensive technique that warrants caution despite lacking a malicious sandbox verdict.
- behaviour.offensiveTechniques also includes T1543.003, although persistenceIndicators and registryKeysSet are empty.
- contactedHosts=null, so no completed host-reputation cross-check is available; 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/74 engines reported a detection.
- 17 tier-1 engines reported no detection.
- Verified signature from CD PROJEKT S.A.
- Established prevalence: 286 sources and 319 submissions.
- Five of five signer-matched historical files received clean outcomes.
- Sandbox mapping includes MITRE T1055 Process Injection.
- Sandbox mapping includes MITRE T1543.003 Windows Service.
- No completed contacted-host reputation cross-check is available.
Use the DLL if it came with an official CD PROJEKT installation or update. If its location or origin is unexpected, confirm the verified signature and reacquire it from the official source 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
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
- 13MITRE ATT&CK techniques
- 9spawned processes
- 0network contacts
- 7filesystem & 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
POCO
019ebd418c64d468fe4a3ef52216c659267e7146fec9e89b3713f135365d7411
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\Desktop\PocoFoundation.dll",#1
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\System32\loaddll64.exe loaddll64.exe "C:\Users\user\Desktop\PocoFoundation.dll"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Logs
C:\ProgramData\Microsoft\Windows Security Health\Logs
04Isolated runtime analysis - Written fileObserved
Connect
\Device\ConDrv\\Connect
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 Security Health\Logs
- \Device\ConDrv\\Connect
- \Sessions\1\BaseNamedObjects\Local\SessionImmersiveColorMutex
- \BaseNamedObjects\Local\SM0:6016:304:WilStaging_02
- \BaseNamedObjects\Local\SM0:6016:120:WilError_03
- \BaseNamedObjects\Local\ZonesCacheCounterMutex
- \BaseNamedObjects\Local\ZonesLockedCacheCounterMutex
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
- 286sources 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 286 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: POCO — 019ebd418c64d468fe4a3ef52216c659267e7146fec9e89b3713f135365d7411
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\Desktop\PocoFoundation.dll",#1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\System32\loaddll64.exe loaddll64.exe "C:\Users\user\Desktop\PocoFoundation.dll"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Logs — C:\ProgramData\Microsoft\Windows Security Health\Logs
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
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.
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\PocoFoundation.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
- POCO
- Format
- Win32 DLL
- Code signing
- Signature valid: CD PROJEKT S.A.
- Size
- 1.9 MB
- Last analyzed
- Sep 23, 2026, 4:42 AM UTC
019ebd418c64d468fe4a3ef52216c659267e7146fec9e89b3713f135365d7411Safety & 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
Open it only when its sender or download source is one 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 POCO safe?
What is POCO?
How many antivirus engines detected POCO?
Is POCO digitally signed?
What is the SHA-256 hash of POCO?
Is it safe to open POCO?
How up to date is this analysis of POCO?
Community
Member reviews and reports for this exact file hash.