Is REDEngineErrorReporter.exe safe?
No engines detected malware, the CD PROJEKT signature verifies, and broad established prevalence outweighs unresolved direct-IP traffic seen during one sandbox run.
All 74 antivirus engines returned no malware or suspicious detection, including 17 tier-1 engines. The verified CD PROJEKT signature, established prevalence, five consistent signer-matched files, and lack of offensive sandbox techniques strongly support legitimate software, although the reputation of observed IP contacts was not checked.
f3cba8150ca66fbdf1…de01c687bb686aRecommended next actions
Before running
Run it only when it came from the developer's official site or another source you independently trust.
If you already ran 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 malware or suspicious detection, including 17 tier-1 engines. The verified CD PROJEKT signature, established prevalence, five consistent signer-matched files, and lack of offensive sandbox techniques strongly support legitimate software, although the reputation of observed IP contacts was not checked.
The sample received no malware or suspicious detections from 74 engines, with all 17 tier-1 participants reporting no detection. Its signature verifies as CD PROJEKT S.A., and there is no detected conflict between the claimed brand and signer. It is established across 265 sources and 302 submissions, while five signer-matched files previously received clean assessments. One completed sandbox run produced no malicious verdict or offensive-only technique, and no inspected child was identified as malware. A medium direct-IP heuristic remains a counter-signal, but no complete host-reputation result is available and the broader evidence does not corroborate command-and-control activity.
What We Detected
No malware or suspicious detections were reported by 74 antivirus engines. The executable has a verified CD PROJEKT S.A. signature, no detected brand mismatch, and established circulation across 265 sources and 302 submissions. Five prior files matched by signer also received clean assessments with 0/74 detections.
Threat Behavior
One completed sandbox run recorded 12 common environmental and application techniques, but no offensive-only techniques or malicious sandbox verdict. One dropped child was inspected and was not identified as malicious, although its individual classification remains unavailable. The sample contacted several IP addresses directly, triggering a medium heuristic; because host-reputation checking was not completed or saved, those contacts cannot be described as clean or known malicious.
What To Do Now
Use the file when it came from an official CD PROJEKT installation or update channel and the digital signature remains valid. If it appeared unexpectedly or outside the expected game directory, verify its source and rescan it while keeping endpoint protection enabled.
Where this verdict could be wrong3 caveats
- MalwareTips.Synth.DirectIpC2 fired because seven external IP addresses were contacted without an application domain; contactedHosts=null leaves their reputation unresolved.
- droppedChildren inspected one child, but its individual verdict is unknown even though droppedChildren.hasMaliciousChild=false.
- signing.signerStats.totalSamples=1 is too small to establish broad historical trust by itself.
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 malware or suspicious content.
- All 17 tier-1 engines reported no detection.
- The signature verifies as CD PROJEKT S.A.
- Prevalence shows 265 sources and 302 submissions.
- Five signer-matched files have prior clean assessments.
- Direct connections to seven external IP addresses triggered MalwareTips.Synth.DirectIpC2.
- No complete reputation cross-check is available for the observed network hosts.
- The dropped child's individual verdict remains unknown.
- Signer history contains only one directly counted sample.
Allow it when obtained through an official CD PROJEKT product or update and the signature validates. If its origin is uncertain, verify the installation source and keep 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
Partial8 runtime contacts were observed without a completed reputation cross-check.
YARA
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
- 12MITRE ATT&CK techniques
- 7spawned processes
- 8network contacts
- 3filesystem & 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
REDEngineErrorReporter.exe
f3cba8150ca66fbdf1fb8c8621ba6db1257d2b644c65a58a2ade01c687bb686a
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\REDEngineErrorReporter.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
%SAMPLEPATH%\REDEngineErrorReporter.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
ConDrv
\Device\ConDrv
04Isolated runtime analysis - Written fileObserved
Connect
\Device\ConDrv\\Connect
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
192.168.0.56
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
20.69.140.28
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 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.
- 192.168.0.56
- 20.69.140.28
- 23.196.193.245
- 184.27.218.92
- 23.216.147.18
- a83f:8110:0:0:4c86:21:0:0
- 23.196.145.221
- 23.46.228.107
- \Device\ConDrv
- \Device\ConDrv\\Connect
- \Sessions\1\BaseNamedObjects\Local\SessionImmersiveColorMutex
Files this sample writes at runtime
This file drops 1 child at runtime. None are currently flagged malicious in our cache.
- 8c2e2510b19e78ecec23…49eb05Never scannednever seen before
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
- 265sources 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 265 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: REDEngineErrorReporter.exe — f3cba8150ca66fbdf1fb8c8621ba6db1257d2b644c65a58a2ade01c687bb686a
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\REDEngineErrorReporter.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — %SAMPLEPATH%\REDEngineErrorReporter.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: ConDrv — \Device\ConDrv
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: Connect — \Device\ConDrv\\Connect
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 192.168.0.56 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 20.69.140.28 — Contact observed during runtime.
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
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
The sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence20.69.140.28 · 23.196.193.245 · 184.27.218.92
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
- REDEngineErrorReporter.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: CD PROJEKT S.A.
- Size
- 256.1 KB
- Last analyzed
- Sep 23, 2026, 5:24 AM UTC
f3cba8150ca66fbdf1fb8c8621ba6db1257d2b644c65a58a2ade01c687bb686aSafety & 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
Run it only when it came 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 REDEngineErrorReporter.exe safe?
What is REDEngineErrorReporter.exe?
How many antivirus engines detected REDEngineErrorReporter.exe?
Is REDEngineErrorReporter.exe digitally signed?
What is the SHA-256 hash of REDEngineErrorReporter.exe?
Is it safe to run REDEngineErrorReporter.exe?
How up to date is this analysis of REDEngineErrorReporter.exe?
Community
Member reviews and reports for this exact file hash.