File scan report
Verdict Safe
Is x360ce.
Only 1 of the 66 antivirus engines that checked it raised a generic detection, while broad prevalence and the absence of corroborating high-risk behaviour strongly indicate a…
Read the whole reasonShow less
Strong evidence · Widely seen for a long time, and nothing harmful found.
Good practice2 tips
We found nothing harmful in this file.
Run it only if it came from the developer's own website or an official app store.
Keep your antivirus and Windows updates switched on.
No scanner can promise a file is 100% safe.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
1 of 66 flagged
- Flagged 1
- No detection 65
- No result 9
- Code signing Unsigned
- Test run Completed
- First seen 10mo ago
Chapter 02
Why we think so
3 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
MaxSecure alone flagged the executable with a generic label; none of the other 74 engines flagged it, including the reporting major engines. Its 745-source history and lack of a named injection target or other high-risk runtime artefact make that isolated detection likely erroneous.
Only 1 of the 66 antivirus engines that checked it flagged the executable, and the sole result came from a less reliable engine using a generic label rather than a named malware family. The major engines that reported results did not flag it. The file has an established distribution history, with 745 distinct sources and 880 submissions since it was first seen on Dec 18, 2025. The sandbox runs recorded no high-risk techniques or named injection target; the bare and mappings do not demonstrate those actions. The executable is unsigned and our static analysis was unavailable, but neither limitation supplies affirmative hostile evidence. Taken together, the isolated detection is highly likely to be a false positive.
What We Detected
Only 1 of the 66 antivirus engines that checked it flagged the executable. MaxSecure applied a generic Trojan label, while no major engine that reported a result corroborated it or identified a malware family.
Threat Behavior
The sandbox runs recorded activity commonly seen in legitimate Windows software and no high-risk technique with a supporting artefact. In particular, no target process was recorded for the T1055 mapping, so it does not establish process injection. The only observed IP contact was identified as analysis-environment background traffic rather than sample activity; a complete host-reputation check was not available.
Context
The file has been submitted by 745 distinct sources a total of 880 times and was first seen on Dec 18, 2025. The antivirus analysis did not identify packing or unusually high-entropy code. The executable is unsigned, and our static analysis was not available, so publisher identity and internal code details were not independently established.
What To Do Now
Use the file only if it came from the expected official distribution channel, and keep security software enabled. If its origin is uncertain or its hash differs from the publisher's release, obtain a fresh copy from the official project source.
Where this verdict could be wrong3 caveats
- MaxSecure labels the file Trojan.Malware.300983.susgen, although no other engine corroborates that generic detection.
- The executable is unsigned, so there is no verified publisher identity anchoring it.
- Our static analysis was unavailable, and no complete contacted-host reputation result 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.
- None of the other 74 engines flagged the file, including the reporting major engines.
- The file has broad, established prevalence across 745 distinct sources and 880 submissions.
- The sandbox runs recorded no high-risk technique backed by a concrete artefact.
- The antivirus analysis found no indication that the executable was packed.
- One engine applied a generic Trojan label.
- The executable has no verified digital signature.
- Internal code inspection and a complete contacted-host reputation check were not available.
6 sources checked · 5 complete · 1 not needed or not applicable. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 18sandbox rule tags
- 2spawned processes
- 0network contacts
- 19filesystem & mutex artifacts
What this file did when executed
This file was run in a sandbox and its runtime behaviour was observed.
Techniques observed in the sandbox
18MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1012
- T1027· Obfuscated code
- T1027.002· Obfuscated code
- T1055· Process injection
- T1056· Keylogging
- T1057· Lists programs
- T1071· Application protocol
- T1082· System recon
- T1083· Scans your files
- T1106
- T1112
- T1115
- T1497· Sandbox evasion
- T1518· Checks your AV
- T1518.001· Checks your AV
- T1547.001· Auto-start
- T1562.001· Disables security
- T1620· In-memory loading
Observed activity
Processes started
2Programs the file ran, with their command lines.
x360ce.exe"C:\Users\<USER>\Desktop\x360ce.exe"x360ce.exe"C:\Users\user\Desktop\x360ce.exe"
Files
15Files the file created, changed or deleted.
- Written
C:\ProgramData\X360CE\Settings\x360ce.Options.xml - Written
C:\ProgramData\X360CE\Settings\x360ce.UserSettings.xml - Written
C:\ProgramData\X360CE\Settings\x360ce.Summaries.xml - Written
C:\ProgramData\X360CE\Settings\x360ce.Programs.xml - Written
C:\ProgramData\X360CE\Settings\x360ce.UserGames.xml - Written
C:\ProgramData\X360CE\Settings\x360ce.Presets.xml
Show all 15 entries for files
- Written
C:\ProgramData\X360CE\Settings\x360ce.UserMacros.xml - Written
C:\ProgramData\X360CE\Settings\x360ce.Layouts.xml - Written
C:\ProgramData\X360CE\Settings\x360ce.PadSettings.xml - Written
C:\ProgramData\X360CE\Settings\x360ce.UserDevices.xml - Written
C:\ProgramData\X360CE\Settings\x360ce.UserInstances.xml - Written
C:\ProgramData\X360CE\Settings\x360ce.XInputMask.xml - Written
C:\ProgramData\X360CE\Temp\ViGEmClient.dll.84A31178\ViGEmClient.dll - Written
C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp - Written
C:\ProgramData\X360CE
Mutexes
4Named locks a program uses so only one copy runs; malware families often reuse them.
X360 Controller EmulatorDirectInput.{5944E682-C92E-11CF-BFC7-444553540000}\Sessions\1\BaseNamedObjects\DBWinMutex\Sessions\1\BaseNamedObjects\X360 Controller Emulator
Sandbox background — not the file
7The analysis machine's own processes and connections, recorded in every run.
- VM process
services.exeC:\Windows\system32\services.exe - VM process
svchost.exeC:\Windows\System32\svchost.exe -k NetworkService -p - VM process
svchost.exeC:\Windows\system32\svchost.exe -k UnistackSvcGroup - VM process
svchost.exeC:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted -p -s StorSvc - VM process
lsass.exeC:\Windows\system32\lsass.exe - VM process
svchost.exeC:\Windows\system32\svchost.exe -k LocalService -s W32Time
Show all 7 entries for sandbox background — not the file
- VM host
162.159.36.2
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache. 10 have no saved verdict and were not checked; that is missing coverage, not a finding.
- 352789a74cb6d9187bfe…4cca92Not checkedno saved verdict
- 43b243da79bcfe5a2e92…726ef8Not checkedno saved verdict
- 44167883a787c7bc0364…e4f99aNot checkedno saved verdict
- d874cca7e90e93fbd217…3b923fNot checkedno saved verdict
- 758cfd9446a8850b43c9…0eba14Not checkedno saved verdict
- 613e34fd780f73e98100…a206fcNot checkedno saved verdict
- 57c26e543061f382aa15…83277cNot checkedno saved verdict
- 9aa4b9ac4e8a18bb2c9e…010732Not checkedno saved verdict
- a61d1c2e1ac1ec273a40…7c32faNot checkedno saved verdict
- 02b50cbe797600959f43…536ba9Not checkedno saved verdict
Chapter 04
Technical details
1 of the 66 antivirus engines that checked it flags it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 1
The saved verdict treats these detections as likely false positives.
- MaxSecureTrojan.Malware.300983.susgen
File fingerprint
- Last analyzed
- Aug 22, 2026, 4:56 PM UTC
- SHA-256
1b0ce29c774e8fecc4018bb04f224719ae87bfa6c9c12b35bcc22e97dae05c5f- SHA-1
4e863356860ebced629c4dcdda6970529a63024d- MD5
9b11488ec508ea3c88dee7d9c842378d
About this file
x360ce.exe is a Win32 EXE file of 14.3 MB.
- Type and size
- Win32 EXE · 14.3 MB
- Signer
- UnsignedNo code signature.
- First seen
- Dec 18, 2025On VirusTotal.
- Submitted by
- 745 distinct sources
- Packer
- None detected
- Entropy
- 7.84 of 8
First scanned Updated
Verdict history
- Suspicious
- Safeafter a re-check of the saved evidence
Ratings change when antivirus engines, our checks or MalwareTips staff learn more about a file.
Antivirus consensus
1 of 66 engines flagged this file
9 of the 75 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
- Tier-115 engines0flagged
- Tier-234 engines0flagged
- Low-trust17 engines1flagged
View all 75 engine results
- MaxSecureMalicious: Trojan.Malware.300983.susgen
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- APEXClean
- ArcabitClean
- AvastNo result
- Avast-MobileNo result
- AVGNo result
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceClean
- CynetClean
- DeepInstinctClean
- DrWebClean
- ElasticClean
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleClean
- GridinsoftClean
- huorongClean
- IkarusNo result
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicNo result
- MalwarebytesClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoClean
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrapmineClean
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaNo result
- ZoneAlarmClean
- ZonerClean
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
VirusTotal's sandbox summary maps this run to MITRE T1055 (Process Injection), but no injected process of the sample's own was recorded (the analysis VM's own WMI adapter, crash handlers and Chrome updater are not counted). VirusTotal maps T1055 on about half of all files no engine flags, so the mapping alone is not evidence of injection.
EvidenceT1055 (sandbox MITRE mapping)
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.
Chapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is x360ce.exe safe?
What is x360ce.exe?
How many antivirus engines detected x360ce.exe?
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.