Is x360ce.exe safe?
Zero engine detections, verified signature, and long-established prevalence outweigh the sandbox heuristics.
No antivirus engine flagged the file across 75 scanners. The executable is signed by Evaldas Jocys and has been submitted by thousands of users since 2020. Sandbox heuristics noted process-injection and LSASS activity, but no malicious verdict or tier-1 consensus exists.
74faf334cb0bdd3e9d…d9aa93a4f6f829Recommended 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.
No antivirus engine flagged the file across 75 scanners. The executable is signed by Evaldas Jocys and has been submitted by thousands of users since 2020. Sandbox heuristics noted process-injection and LSASS activity, but no malicious verdict or tier-1 consensus exists.
The complete absence of detections from 75 reporting engines, including 14 tier-1 engines, is the strongest signal. The file carries a valid digital signature and shows a common_old prevalence pattern consistent with legitimate software. While sandbox traces map to MITRE techniques T1055 and T1543.003, these alone do not override the clean multi-engine result. Similar-hash matches are inconclusive because they lack signer correlation. Contacted-host reputation data is missing, so no complete contacted-host reputation result was available or malicious.
What We Detected
75 engines scanned the sample; 0 returned malicious. The binary is signed by Evaldas Jocys with a verified certificate. Prevalence data shows 21 489 submissions from 3 731 sources since November 2020.
Threat Behavior
One sandbox recorded MITRE techniques T1055 (process injection), T1543.003 (service creation), T1547.001 (registry run keys), T1562.001 (disable security tools), and T1620 (reflective code loading). No malicious sandbox verdict was issued. 14 external IP addresses were contacted, but host-reputation coverage is unavailable.
What To Do Now
Keep endpoint protection enabled. If the file is required for Xbox 360 controller emulation, obtain it only from the official Jocys.com distribution channel and verify the digital signature before execution.
Where this verdict could be wrong3 caveats
- triggeredHeuristics show 'MalwareTips.Synth.ProcessInjection' and 'MalwareTips.Synth.CredentialDumper' on LSASS access (T1055, T1543.003)
- contactedHosts=null — 14 IPs observed but no reputation result available
- similarHashes contain one 'malicious' verdict (extremeinjector) on same imphash
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/75 engines flagged the file
- Verified digital signature present
- Established prevalence since 2020
- Sandbox heuristics flagged LSASS access and process injection
- 14 direct-IP connections observed without domain context
- High-entropy code section (.text entropy 7.84)
The file can be considered safe for its stated purpose; continue normal security hygiene and obtain future updates only from the legitimate publisher.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial20 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete3 signature or behavior rules 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
- 26MITRE ATT&CK techniques
- 15spawned processes
- 20network contacts
- 40filesystem & 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
x360ce.exe
74faf334cb0bdd3e9dfab8c323d4eb3b9b089bcaadc7dbd639d9aa93a4f6f829
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\executable.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\services.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
x360ce.Options.xml
C:\ProgramData\X360CE\Settings\x360ce.Options.xml
04Isolated runtime analysis - Written fileObserved
x360ce.UserSettings.xml
C:\ProgramData\X360CE\Settings\x360ce.UserSettings.xml
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
192.168.0.4
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
a83f:8110:8788:ffff:0:0:0:0
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.4
- a83f:8110:8788:ffff:0:0:0:0
- 20.80.129.13
- 192.168.0.80
- 192.168.0.57
- 192.168.0.106
- 131.253.33.203
- 23.216.147.64
- 72.21.81.240
- a83f:8110:1800:0:0:0:0:0
- C:\ProgramData\X360CE\Settings\x360ce.Options.xml
- C:\ProgramData\X360CE\Settings\x360ce.UserSettings.xml
- C:\ProgramData\X360CE\Settings\x360ce.Summaries.xml
- C:\ProgramData\X360CE\Settings\x360ce.Programs.xml
- C:\ProgramData\X360CE\Settings\x360ce.UserGames.xml
- C:\Windows\System32\spp\store\2.0\cache\cache.dat
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER4B5C.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER4D30.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER4D60.tmp.txt
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER5407.tmp.WERInternalMetadata.xml
- X360 Controller Emulator
- DirectInput.{89521361-AA8A-11CF-BFC7-444553540000}
- DirectInput.{5944E682-C92E-11CF-BFC7-444553540000}
- DBWinMutex
- \Sessions\1\BaseNamedObjects\Local\SM0:1196:304:WilStaging_02
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 55cb9a80ed7ecd54c556…353266Never scannednever seen before
- 352789a74cb6d9187bfe…4cca92Never scannednever seen before
- 44167883a787c7bc0364…e4f99aNever scannednever seen before
- d874cca7e90e93fbd217…3b923fNever scannednever seen before
- 758cfd9446a8850b43c9…0eba14Never scannednever seen before
- 613e34fd780f73e98100…a206fcNever scannednever seen before
- 57c26e543061f382aa15…83277cNever scannednever seen before
- 9aa4b9ac4e8a18bb2c9e…010732Never scannednever seen before
- a61d1c2e1ac1ec273a40…7c32faNever scannednever seen before
- 02b50cbe797600959f43…536ba9Never 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.
- 3rule hits recorded
- 0 / 75engines flagged
- 3,731sources 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 75 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 3,731 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
The file has a valid code signature from Evaldas Jocys.
ProvenanceObservedSourceCode-signing metadataObserved at - 04
Scanned file: x360ce.exe — 74faf334cb0bdd3e9dfab8c323d4eb3b9b089bcaadc7dbd639d9aa93a4f6f829
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\executable.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\services.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: x360ce.Options.xml — C:\ProgramData\X360CE\Settings\x360ce.Options.xml
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: x360ce.UserSettings.xml — C:\ProgramData\X360CE\Settings\x360ce.UserSettings.xml
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 192.168.0.4 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: a83f:8110:8788:ffff:0:0:0:0 — 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
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.
EvidenceC:\Windows\System32\svchost.exe -k NetworkService -pSandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.
EvidenceC:\Windows\system32\lsass.exeThe 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.
Evidencea83f:8110:8788:ffff:0:0:0:0 · 20.80.129.13 · 131.253.33.203
0 of 75 engines flagged this file
View all 75 engine results
Section entropy & packers
Executable sections have high entropy (7.2+) — the code is compressed or encrypted and only decrypted at runtime. Classic packing behaviour.
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
- x360ce.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: Evaldas Jocys
- Size
- 14.7 MB
- Last analyzed
- Aug 22, 2026, 5:00 PM UTC
74faf334cb0bdd3e9dfab8c323d4eb3b9b089bcaadc7dbd639d9aa93a4f6f829Safety & 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 x360ce.exe safe?
What is x360ce.exe?
How many antivirus engines detected x360ce.exe?
Is x360ce.exe digitally signed?
What is the SHA-256 hash of x360ce.exe?
Is it safe to run x360ce.exe?
How up to date is this analysis of x360ce.exe?
Community
Member reviews and reports for this exact file hash.