Is POCO safe?
No antivirus engine detected the established, CD PROJEKT-signed DLL, while matching publisher samples consistently received benign assessments despite one isolated T1055 mapping.
All 74 antivirus engines returned no detection, including 17 tier-1 engines, and the DLL carries a verified CD PROJEKT S.A. signature. Its broad, established prevalence and five publisher-matched prior assessments strongly support legitimate software, while the isolated T1055 mapping lacks corroborating sandbox or network evidence.
8b8f5f5d772a4d839f…37d21af5e1c474Recommended 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 74 antivirus engines returned no detection, including 17 tier-1 engines, and the DLL carries a verified CD PROJEKT S.A. signature. Its broad, established prevalence and five publisher-matched prior assessments strongly support legitimate software, while the isolated T1055 mapping lacks corroborating sandbox or network evidence.
The file produced no detections across 74 antivirus engines, with all 17 reporting tier-1 engines remaining silent. Its signature verifies to CD PROJEKT S.A., and no conflicting brand identity was detected. The sample has appeared across 281 sources and 317 submissions, which is consistent with established commodity software rather than an isolated payload. Five signer-matched files previously received safe assessments, including three similarly named POCO files. One sandbox mapped activity to T1055, but it recorded no malicious sandbox verdict, persistence, dropped payload, or registry modification; a complete contacted-host reputation result is unavailable.
What We Detected
No detections were returned by 74 antivirus engines, including 17 tier-1 engines. The DLL is signed with a verified certificate belonging to CD PROJEKT S.A., and its product identity does not conflict with that signer. It is also well established, appearing in 317 submissions from 281 sources.
Threat Behavior
One completed sandbox mapped activity to MITRE T1055, which can relate to process injection. However, the available execution record does not prove a specific injection method or hostile intent, and there was no malicious sandbox verdict, persistence, dropped payload, or registry modification. No network contacts were recorded, although a separate contacted-host reputation cross-check was not saved.
What To Do Now
The evidence strongly supports this being a legitimate signed library associated with established software. Keep endpoint protection enabled and obtain the file from the official game installation or distribution channel; investigate further only if its signature later fails verification or it appears outside the expected application directory.
Where this verdict could be wrong3 caveats
- behaviour.offensiveTechniques includes T1055, indicating possible process-injection-related activity; the saved evidence does not establish the precise method or malicious intent.
- signing.signerStats.totalSamples=1 provides little standalone history, although five independent signer-matched prior verdicts support the publisher pattern.
- contactedHosts=null, so no complete contacted-host reputation cross-check 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 detected the sample.
- All 17 reporting tier-1 engines were clean.
- Verified signature from CD PROJEKT S.A.
- 281 sources and 317 submissions indicate established prevalence.
- Five of five signer-matched prior files received safe verdicts.
- One sandbox mapped activity to MITRE T1055.
- The DLL was exercised through rundll32 during analysis.
- No complete contacted-host reputation cross-check is available.
Keep endpoint protection enabled and use the DLL only as part of software obtained through an official CD PROJEKT distribution channel. 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 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
- 8MITRE 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
8b8f5f5d772a4d839f6f73e474877c4568c1ce733ae006bd8237d21af5e1c474
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\Desktop\PocoJSON.dll",#1
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\System32\loaddll64.exe loaddll64.exe "C:\Users\user\Desktop\PocoJSON.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:6324:304:WilStaging_02
- \BaseNamedObjects\Local\SM0:6324: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
- 281sources 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 281 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 — 8b8f5f5d772a4d839f6f73e474877c4568c1ce733ae006bd8237d21af5e1c474
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\Desktop\PocoJSON.dll",#1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\System32\loaddll64.exe loaddll64.exe "C:\Users\user\Desktop\PocoJSON.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\PocoJSON.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
- 377.1 KB
- Last analyzed
- Sep 23, 2026, 4:43 AM UTC
8b8f5f5d772a4d839f6f73e474877c4568c1ce733ae006bd8237d21af5e1c474Safety & 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.