Is ebonhold_1.0.5_x64-setup.exe safe?
Suspicious file assessment
3 high-confidence signature or behavior rules matched this file.
8680fac1ecd0b0ce58…9399206f7a7e26Recommended next actions
Before installing
Do not install it until the source and publisher can be verified independently.
If you already installed it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Download a fresh installer from the developer's official site or an official app store.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
No saved analyst narrative
This report keeps the verified scan facts available below without inventing an analysis that was not saved with the scan.
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
Complete5 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
- 21MITRE ATT&CK techniques
- 11spawned processes
- 1network contacts
- 23filesystem & 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: Changed an auto-start location that can make code run after sign-in or restart.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Scans through your files and folders.
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
ebonhold_1.0.5_x64-setup.exe
8680fac1ecd0b0ce58e99dcbe5c9764c8842bf69af75cfb9699399206f7a7e26
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\ebonhold_1.0.5_x64-setup.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\Explorer.EXE
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
nssC66D.tmp
C:\Users\<USER>\AppData\Local\Temp\nssC66D.tmp
04Isolated runtime analysis - Written fileObserved
System.dll
C:\Users\<USER>\AppData\Local\Temp\nssC66E.tmp\System.dll
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:\Users\<USER>\AppData\Local\Temp\nssC66D.tmp
- C:\Users\<USER>\AppData\Local\Temp\nssC66E.tmp\System.dll
- C:\Users\<USER>\AppData\Local\Temp\nssC66E.tmp\modern-wizard.bmp
- C:\Users\<USER>\AppData\Local\Temp\nssC66E.tmp\nsDialogs.dll
- C:\Users\<USER>\AppData\Local\Temp\nssC66E.tmp\nsis_tauri_utils.dll
- C:\Users\<USER>\AppData\Local\Packages\Microsoft.XboxGamingOverlay_8wekyb3d8bbwe\LocalCache\KnownGameList.bin
- C:\Users\<USER>\AppData\Local\Microsoft\GameDVR\KnownGameList.update
- C:\Users\<USER>\AppData\Local\Temp\nsqD284.tmp
- C:\Users\<USER>\AppData\Local\Temp\nsvD2F3.tmp
- C:\Users\user\AppData\Local\Temp\nsn4DDF.tmp
- cversions.3.m
- Global\OneSettingQueryMutex+compat+encapsulation
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- e153bf80f73051aae8f0…f78258Never scannednever seen before
- 6a32397b51babc7673c3…bfe955Never scannednever seen before
- f942c40a34155aa4ead3…6bc2c5Never scannednever seen before
- aade2b63fc1e6cccdf2f…15cd88Never scannednever seen before
- b1350f487692057c8ffd…551fc0Never scannednever seen before
- 3860bb6d19ed159f91e0…7ec35aNever scannednever seen before
- 9baee42d66f715bba878…b40256Never scannednever seen before
- 807590c24c354a943b8b…1eca52Never scannednever seen before
- 8fc936ee48511dc4170d…1516e2Never scannednever seen before
- 8b4c47c4cf5e76ec57dd…90d37cNever 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.
- 5rule hits recorded
- 1 / 75engines flagged
- 122sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
3 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 Sophos.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
YARAify matched 2 researcher rules to this file.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: ebonhold_1.0.5_x64-setup.exe — 8680fac1ecd0b0ce58e99dcbe5c9764c8842bf69af75cfb9699399206f7a7e26
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\ebonhold_1.0.5_x64-setup.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\Explorer.EXE
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: nssC66D.tmp — C:\Users\<USER>\AppData\Local\Temp\nssC66D.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: System.dll — C:\Users\<USER>\AppData\Local\Temp\nssC66E.tmp\System.dll
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.
One or more independent reference databases matched 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.
- Detect_NSIS_Nullsoft_Installer
- PE_Digital_Certificate
MITRE T1055 (Process Injection) observed — CreateRemoteThread / APC / reflective-DLL injection. The payload is being smuggled into a legitimate process to bypass AV hooks.
EvidenceC:\Windows\Explorer.EXESandbox 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.2
1 of 75 engines flagged this file
View all 75 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
Lots of people are uploading this but it's recent — typical of newly-released legitimate software. Low prior for malware.
Fingerprint and provenance
- File name
- ebonhold_1.0.5_x64-setup.exe
- Format
- Win32 EXE
- Code signing
- Signature not verified: EbonholdLauncher
- Size
- 10.2 MB
- Last analyzed
- Jun 25, 2026, 7:55 PM UTC
8680fac1ecd0b0ce58e99dcbe5c9764c8842bf69af75cfb9699399206f7a7e26Safety & 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 install 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. Download a fresh installer 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 ebonhold_1.0.5_x64-setup.exe safe, or is it malware?
What is ebonhold_1.0.5_x64-setup.exe?
How many antivirus engines detected ebonhold_1.0.5_x64-setup.exe?
I already downloaded and installed ebonhold_1.0.5_x64-setup.exe — what should I do?
How do I remove ebonhold_1.0.5_x64-setup.exe?
Is ebonhold_1.0.5_x64-setup.exe digitally signed?
What is the SHA-256 hash of ebonhold_1.0.5_x64-setup.exe?
How up to date is this analysis of ebonhold_1.0.5_x64-setup.exe?
Community
Member reviews and reports for this exact file hash.