Is POCO safe?
No antivirus engine detected the established, CD PROJEKT-signed DLL, while broad prevalence and matching publisher history outweigh one uncorroborated T1055 mapping.
All 72 antivirus engines returned no detection, including 17 tier-1 engines, and the DLL has a verified CD PROJEKT S.A. signature. It is widely established and matches four previously accepted files from the same signer; one sandbox mapped activity to T1055, but produced no malicious verdict or supporting persistence, payload, or network evidence.
b914fa716ac083db19…feba1d2ac73ce7Recommended 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.
All 72 antivirus engines returned no detection, including 17 tier-1 engines, and the DLL has a verified CD PROJEKT S.A. signature. It is widely established and matches four previously accepted files from the same signer; one sandbox mapped activity to T1055, but produced no malicious verdict or supporting persistence, payload, or network evidence.
The DLL received no malicious or suspicious detections from 72 antivirus engines, with all 17 participating tier-1 engines reporting no detection. Its signature verifies to CD PROJEKT S.A., and there is no detected conflict between the claimed brand and signer. The file has appeared through 316 sources across 347 submissions, which strongly reduces concern that it is an unfamiliar payload. Four signer-matched files previously received safe outcomes, reinforcing the publisher context. One completed sandbox mapped execution to T1055, but it did not issue a malicious verdict, record persistence, drop another payload, or observe network contacts, so that isolated behavioral mapping does not outweigh the broader evidence.
What We Detected
None of 72 antivirus engines flagged this Win32 DLL, and all 17 tier-1 engines that participated reported no detection. The file carries a verified signature from CD PROJEKT S.A., has no detected brand mismatch, and has been submitted 347 times by 316 distinct sources.
Threat Behavior
One sandbox run mapped execution through rundll32 to MITRE T1055, which can be associated with process injection. That run did not produce a malicious sandbox verdict, establish persistence, drop another file, or record contacted domains, IP addresses, or URLs. No complete host-reputation cross-check was saved, though there were no observed contacts requiring assessment. Static PE analysis also found no packer, no likely packing, and no high-entropy code section.
What To Do Now
The evidence is consistent with an established publisher component. Keep endpoint protection enabled and use the DLL only as part of software obtained through an official or otherwise trusted installation source; investigate again if its signature becomes invalid or it appears outside the expected product directory.
Where this verdict could be wrong2 caveats
- behaviour.offensiveTechniques contains T1055 from one sandbox run; this process-injection mapping is a meaningful risk signal, although no sandbox produced a malicious verdict.
- contactedHosts=null, so no completed host-reputation cross-check is available; however, 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/72 antivirus engines reported a malicious or suspicious result.
- 17/17 reporting tier-1 engines returned no detection.
- Verified signature from 'CD PROJEKT S.A.' with no brand mismatch.
- Common, established prevalence: 316 sources and 347 submissions.
- 4/4 similar signer-matched files previously received safe verdicts.
- One sandbox mapped execution activity to MITRE T1055.
- Only one completed sandbox observation is available.
- signing.signerStats.totalSamples=1, so direct historical signer statistics remain limited.
- contactedHosts=null, meaning no saved host-reputation cross-check is available.
Use the DLL when it comes from the expected CD PROJEKT installation or update channel, and keep endpoint protection enabled. Recheck the signature and installation path if the file appeared unexpectedly.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 72 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
- 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
b914fa716ac083db19f84281e9d1a0ce435d8807a1f9b3d335feba1d2ac73ce7
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\Desktop\PocoData.dll",#1
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\System32\loaddll64.exe loaddll64.exe "C:\Users\user\Desktop\PocoData.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:2932:304:WilStaging_02
- \BaseNamedObjects\Local\SM0:2932: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 / 72engines flagged
- 316sources 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 72 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 316 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 — b914fa716ac083db19f84281e9d1a0ce435d8807a1f9b3d335feba1d2ac73ce7
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\Desktop\PocoData.dll",#1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\System32\loaddll64.exe loaddll64.exe "C:\Users\user\Desktop\PocoData.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\PocoData.dll",#1
0 of 72 engines flagged this file
View all 72 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.8 MB
- Last analyzed
- Sep 23, 2026, 4:39 AM UTC
b914fa716ac083db19f84281e9d1a0ce435d8807a1f9b3d335feba1d2ac73ce7Safety & 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.