Is POCO safe?
No engine detected this established, verified CD PROJEKT DLL, while prevalence and five signer-matched prior samples strongly support legitimate commodity software.
None of 74 antivirus engines flagged the DLL, including all 17 reporting tier-1 engines. Its verified CD PROJEKT signature, established prevalence, and five signer-matched prior samples support legitimate software; the isolated T1055 mapping lacks a malicious sandbox verdict or corroborating artifacts.
aaf856dcea277b53a5…befbe6a19e55f5Recommended 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.
None of 74 antivirus engines flagged the DLL, including all 17 reporting tier-1 engines. Its verified CD PROJEKT signature, established prevalence, and five signer-matched prior samples support legitimate software; the isolated T1055 mapping lacks a malicious sandbox verdict or corroborating artifacts.
The sample received no malicious or suspicious detections from 74 engines, with all 17 reporting tier-1 engines silent. Its signature verifies to CD PROJEKT S.A., and no publisher mismatch was identified. The file has circulated for 431 days across 284 sources, while five signer-matched historical samples were previously assessed as benign. One sandbox mapped activity to T1055, but produced no malicious verdict, persistence evidence, or dropped payload. No complete contacted-host reputation result is available, although the sandbox recorded no domains, IP addresses, or URLs.
What We Detected
No malicious or suspicious detections appeared among 74 antivirus engines, including 17 tier-1 engines. The DLL carries a verified CD PROJEKT S.A. signature, and no brand mismatch was identified. It is also well established, with 313 submissions from 284 sources over 431 days, while five prior signer-matched files received benign assessments.
Threat Behavior
One completed sandbox mapped activity to MITRE T1055, which can represent process injection. That mapping is a cautionary signal, but it was not accompanied by a malicious sandbox verdict, persistence changes, dropped payloads, or observed network contacts. No complete contacted-host reputation cross-check is available because that result was not saved.
What To Do Now
Keep endpoint protection enabled and obtain the DLL through an official CD PROJEKT installation or update channel. If it appeared unexpectedly or outside its normal application directory, verify the signature and reinstall the associated product from its official source.
Where this verdict could be wrong3 caveats
- behaviour.offensiveTechniques includes T1055 (Process Injection), although the saved evidence does not establish the exact injection method or malicious intent.
- signing.signerStats.totalSamples=1 provides limited direct historical depth, though five separate signer-matched prior decisions support the same publisher.
- contactedHosts=null, so no completed host-reputation cross-check is available; the observed sandbox contact lists were empty.
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 malicious or suspicious result.
- All 17 reporting tier-1 engines returned no detection.
- The signature is verified for CD PROJEKT S.A.
- The file has 313 submissions from 284 sources over 431 days.
- Five of five signer-matched historical samples received safe verdicts.
- One sandbox mapped runtime activity to MITRE T1055 (Process Injection).
- The direct signer history contains only signing.signerStats.totalSamples=1.
- contactedHosts=null, leaving the host-reputation cross-check incomplete.
Use the file if it came with an official CD PROJEKT product and its signature remains valid. Keep endpoint protection enabled and replace it from the official installer if its origin is uncertain.
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
- 10MITRE 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
aaf856dcea277b53a5a2205e1fd035777d093f33d761170e76befbe6a19e55f5
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\Desktop\PocoDataSQLite.dll",#1
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\System32\loaddll64.exe loaddll64.exe "C:\Users\user\Desktop\PocoDataSQLite.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:6980:304:WilStaging_02
- \BaseNamedObjects\Local\SM0:6980: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
- 284sources 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 284 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 — aaf856dcea277b53a5a2205e1fd035777d093f33d761170e76befbe6a19e55f5
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\Desktop\PocoDataSQLite.dll",#1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\System32\loaddll64.exe loaddll64.exe "C:\Users\user\Desktop\PocoDataSQLite.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\PocoDataSQLite.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
- 401.6 KB
- Last analyzed
- Sep 23, 2026, 4:40 AM UTC
aaf856dcea277b53a5a2205e1fd035777d093f33d761170e76befbe6a19e55f5Safety & 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.