Is x360ce.exe safe?
Unsigned packed executable with low-trust detection and sandbox-observed LSASS access plus direct-IP traffic.
One low-trust engine flagged the file; no tier-1 detections. Runtime evidence shows process-injection and credential-store activity, yet sandbox returned no malicious verdict and external intel is clean. Mixed signals leave the file in suspicious territory.
1b0ce29c774e8fecc4…c22e97dae05c5fRecommended next actions
Before running
Do not run it until the source and publisher can be verified independently.
If you already ran it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the developer's official site or an official app store.
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.
One low-trust engine flagged the file; no tier-1 detections. Runtime evidence shows process-injection and credential-store activity, yet sandbox returned no malicious verdict and external intel is clean. Mixed signals leave the file in suspicious territory.
The single malicious label comes from a low-trust engine and is unsupported by any tier-1 product. The unsigned status removes any signer-history benefit. Sandbox telemetry records LSASS access and direct-no complete contacted-host reputation result was available and contacted-host reputation data is missing. Similar-hash history is split, and prevalence is high, yet the combination of packing, offensive MITRE techniques, and lack of corroboration keeps the sample in the suspicious band.
What We Detected
75 engines scanned the sample; only MaxSecure returned a malicious result (Trojan.Malware.300983.susgen). No tier-1 engine flagged the file. The binary is unsigned, packed, and exhibits high-entropy code sections.
Threat Behavior
Sandbox execution recorded four offensive MITRE techniques (T1055 process injection, T1547.001 persistence, T1562.001 defense evasion, T1620 reflective loading) plus direct-IP contact to 162.159.36.2. LSASS memory access was observed, but the sandbox did not classify the run as malicious. Ten dropped children were inspected; none carried malicious verdicts.
What To Do Now
Do not execute the file on production systems. Keep endpoint protection enabled. If the file is required for legitimate controller-emulation purposes, obtain it from the official x360ce project site and verify its digital signature or checksum against the publisher.
Where this verdict could be wrong1 caveat
- contactedHosts=null — host-reputation cross-check incomplete; cannot confirm whether 162.159.36.2 is malicious.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Only 1/75 engines flagged malicious
- No tier-1 detections
- High prevalence (common_old)
- No malicious dropped children
- Unsigned executable
- High-entropy packed code
- Sandbox observed LSASS access
- Direct-IP network contact without domain
- Imphash match to known hacktool sample
Treat the file as suspicious; run it only in an isolated environment or replace it with a verified build from the legitimate source.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
Complete4 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
- 18MITRE ATT&CK techniques
- 8spawned processes
- 1network contacts
- 19filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Used an input-capture technique that can record credentials or keystrokes.
High concern: Changed an auto-start location that can make code run after sign-in or restart.
High concern: Attempted to impair or bypass security controls.
High concern: Loaded code directly into memory instead of from a normal file.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
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
1b0ce29c774e8fecc4018bb04f224719ae87bfa6c9c12b35bcc22e97dae05c5f
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\x360ce.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
162.159.36.2
Contact observed during runtime.
06Isolated runtime analysis
6 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.
- 162.159.36.2
- 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
- X360 Controller Emulator
- DirectInput.{5944E682-C92E-11CF-BFC7-444553540000}
- \Sessions\1\BaseNamedObjects\DBWinMutex
- \Sessions\1\BaseNamedObjects\X360 Controller Emulator
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 352789a74cb6d9187bfe…4cca92Never scannednever seen before
- 43b243da79bcfe5a2e92…726ef8Never 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.
- 4rule hits recorded
- 1 / 75engines flagged
- 745sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
2 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
1 of 75 antivirus engines flagged the file, including MaxSecure.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has a long, established submission history across 745 sources.
ProvenanceDerivedSourceSubmission historyObserved at - 04
Scanned file: x360ce.exe — 1b0ce29c774e8fecc4018bb04f224719ae87bfa6c9c12b35bcc22e97dae05c5f
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\x360ce.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: 162.159.36.2 — 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.
Evidence162.159.36.2Unsigned, packed PE with sandbox-observed network activity. The packing step hides the payload until execution; the network call fetches / reports for the next stage. Classic dropper / stager behaviour.
Evidence162.159.36.2
1 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
- No verified publisher
- Size
- 13.6 MB
- Last analyzed
- Aug 22, 2026, 4:56 PM UTC
1b0ce29c774e8fecc4018bb04f224719ae87bfa6c9c12b35bcc22e97dae05c5fSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't run it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source. Get a fresh copy from the developer's official site or an official app store.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is x360ce.exe safe, or is it malware?
What is x360ce.exe?
How many antivirus engines detected x360ce.exe?
I already downloaded and ran x360ce.exe — what should I do?
How do I remove x360ce.exe?
What is the SHA-256 hash of x360ce.exe?
How up to date is this analysis of x360ce.exe?
Community
Member reviews and reports for this exact file hash.