Is Alpine_Client_Setup_1_8_5_x86_64_8dd1bd0c66.exe safe?
Installer shows process-injection and LSASS-access signals plus YARA hits, yet zero AV detections and common-old prevalence.
The file is a signed Inno Setup installer that triggered sandbox heuristics for process injection and LSASS access, plus six YARA rules. No antivirus engine flagged it, and the sample has been submitted over a thousand times without a confirmed malicious family.
7d98f239dd3585dd8d…fe75265aafd5ecRecommended 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.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
The file is a signed Inno Setup installer that triggered sandbox heuristics for process injection and LSASS access, plus six YARA rules. No antivirus engine flagged it, and the sample has been submitted over a thousand times without a confirmed malicious family.
Zero detections across 75 engines and a verified signature reduce the likelihood of commodity malware. However, the sandbox recorded T1055 process injection, T1134 token manipulation, and LSASS access, and YARAify matched six community rules including an injection detector. Similar imphash samples have produced mixed verdicts, and the signer has no historical track record. These conflicting signals place the file in the suspicious band.
What We Detected
75 engines scanned the 7.5 MB executable; none returned a malicious or suspicious result. The binary is signed by 'CRYSTAL DEVELOPMENT' and verified. Sandbox execution recorded four MITRE techniques normally associated with offensive tooling: T1055 (process injection), T1134/T1134.004 (token manipulation), and T1485 (data destruction). YARAify matched six rules, among them 'CP_Script_Inject_Detector' and 'HUNTING_SUSP_TLS_SECTION'. Ten dropped children were inspected; none carried a malicious verdict.
Threat Behavior
The installer writes files to %LocalAppData%\Programs\Alpine Client and spawns 'pinnacle-windows-amd64.exe'. Observed outbound traffic used direct IP addresses rather than domains. No persistence mechanisms or registry modifications were recorded. The contacted hosts cache returned no prior malicious entries.
What To Do Now
Keep Windows Defender and other endpoint protection enabled. If the file originated from an official Alpine Client distribution channel, compare its SHA-256 against the vendor's published checksum. Otherwise, avoid execution until additional corroboration is available.
Where this verdict could be wrong2 caveats
- YARAify returned 6 rule hits, but rules are generic (Borland, TLS callbacks, digital certificate) rather than family-specific malware signatures.
- Community comment claims 'Malware' with score 100/100, yet no engine detection corroborates that claim.
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 sample
- Verified digital signature present
- common_old prevalence (1223 submitters)
- No malicious dropped children or contacted hosts
- Sandbox observed T1055 process injection
- Sandbox observed LSASS access (T1134)
- YARAify matched 6 community rules
- Signer 'CRYSTAL DEVELOPMENT' has no prior sample history
Treat the installer with caution; run it only inside a disposable VM or after confirming its checksum with the vendor.
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
Partial1 of 6 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete8 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
- 25MITRE ATT&CK techniques
- 15spawned processes
- 6network contacts
- 40filesystem & 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.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Removed execution artefacts or logs, which can conceal activity.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Scans through your files and folders.
Moderate concern: Decoded or unpacked concealed content while running.
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
Alpine_Client_Setup_1_8_5_x86_64_8dd1bd0c66.exe
7d98f239dd3585dd8da29130aacbcda6617584494abfb2ed4bfe75265aafd5ec
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\AlpineClientSetup-1.8.5-x86_64.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\is-IMH11.tmp\AlpineClientSetup-1.8.5-x86_64.tmp" /SL5="$3D01A8,6051439,1370112,C:\Users\<USER>\Desktop\AlpineClientSetup-1.8.5-x86_64.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
AlpineClientSetup-1.8.5-x86_64.tmp
C:\Users\<USER>\AppData\Local\Temp\is-IMH11.tmp\AlpineClientSetup-1.8.5-x86_64.tmp
04Isolated runtime analysis - Written fileObserved
_setup64.tmp
C:\Users\<USER>\AppData\Local\Temp\is-8LGDQ.tmp\_isetup\_setup64.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
104.18.10.102
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
140.82.112.5
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.
- 104.18.10.102
- 140.82.112.5
- 192.168.0.39
- 23.55.140.42
- 151.101.194.133
- http://secure.globalsign.com/cacert/root-r3.crt
- C:\Users\<USER>\AppData\Local\Temp\is-IMH11.tmp\AlpineClientSetup-1.8.5-x86_64.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-8LGDQ.tmp\_isetup\_setup64.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-8LGDQ.tmp\_isetup\_isdecmp.dll
- C:\Users\<USER>\AppData\Local\Programs\Alpine Client\pinnacle-windows-amd64.exe
- C:\Users\<USER>\AppData\Local\Programs\Alpine Client\unins000.dat
- C:\Users\<USER>\AppData\Local\Programs\Alpine Client\is-BBGU8.tmp
- C:\Users\<USER>\AppData\Local\Programs\Alpine Client\is-5QQTN.tmp
- C:\Users\<USER>\AppData\Local\Programs\Alpine Client\is-K2PT9.tmp
- C:\Users\<USER>\AppData\Local\Programs\Alpine Client\is-VTU6C.tmp
- C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Alpine Client\Alpine Client.lnk
- Local\InternetShortcutMutex
- cversions.3.m
- Local\RstrMgr3887CAB8-533F-4C85-B0DC-3E5639F8D511
- Local\RstrMgr-3887CAB8-533F-4C85-B0DC-3E5639F8D511-Session0000
- DefaultTabtip-MainUI
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 2684de17300e0a434686…7c5d50Never scannednever seen before
- 27e22d0d51a70e1a7547…08c8a4Never scannednever seen before
- 9624fc5fec690c911467…e4ceb6Never scannednever seen before
- 16a19763520bc5acfa82…a4042fNever scannednever seen before
- 6a254d08c979361fea14…8f63e8Never scannednever seen before
- 8a4f0a4d144f8fd1ed33…a38f4eNever scannednever seen before
- fc4f2f450025ee0ba84c…10fb87Never scannednever seen before
- 388a796580234efc95f3…136f95Never scannednever seen before
- 8287d0e287a66ee78537…a57e64Never scannednever seen before
- eae0de6984b220f60d58…4dc0d7Never 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.
- 8rule hits recorded
- 0 / 75engines flagged
- 1,223sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
6 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
0 of 75 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has a long, established submission history across 1,223 sources.
ProvenanceDerivedSourceSubmission historyObserved at - 04
Scanned file: Alpine_Client_Setup_1_8_5_x86_64_8dd1bd0c66.exe — 7d98f239dd3585dd8da29130aacbcda6617584494abfb2ed4bfe75265aafd5ec
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\AlpineClientSetup-1.8.5-x86_64.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\<USER>\AppData\Local\Temp\is-IMH11.tmp\AlpineClientSetup-1.8.5-x86_64.tmp" /SL5="$3D01A8,6051439,1370112,C:\Users\<USER>\Desktop\AlpineClientSetup-1.8.5-x86_64.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: AlpineClientSetup-1.8.5-x86_64.tmp — C:\Users\<USER>\AppData\Local\Temp\is-IMH11.tmp\AlpineClientSetup-1.8.5-x86_64.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: _setup64.tmp — C:\Users\<USER>\AppData\Local\Temp\is-8LGDQ.tmp\_isetup\_setup64.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 104.18.10.102 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 140.82.112.5 — 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.
- Borland
- CP_Script_Inject_Detector
- HUNTING_SUSP_TLS_SECTION
- pe_detect_tls_callbacks
- PE_Digital_Certificate
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\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.
Evidence104.18.10.102 · 140.82.112.5 · 23.55.140.42
0 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
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
- Alpine_Client_Setup_1_8_5_x86_64_8dd1bd0c66.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: CRYSTAL DEVELOPMENT
- Size
- 7.2 MB
- Last analyzed
- Sep 6, 2026, 7:59 AM UTC
7d98f239dd3585dd8da29130aacbcda6617584494abfb2ed4bfe75265aafd5ecSafety & 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 Alpine_Client_Setup_1_8_5_x86_64_8dd1bd0c66.exe safe, or is it malware?
What is Alpine_Client_Setup_1_8_5_x86_64_8dd1bd0c66.exe?
How many antivirus engines detected Alpine_Client_Setup_1_8_5_x86_64_8dd1bd0c66.exe?
I already downloaded and installed Alpine_Client_Setup_1_8_5_x86_64_8dd1bd0c66.exe — what should I do?
How do I remove Alpine_Client_Setup_1_8_5_x86_64_8dd1bd0c66.exe?
Is Alpine_Client_Setup_1_8_5_x86_64_8dd1bd0c66.exe digitally signed?
What is the SHA-256 hash of Alpine_Client_Setup_1_8_5_x86_64_8dd1bd0c66.exe?
How up to date is this analysis of Alpine_Client_Setup_1_8_5_x86_64_8dd1bd0c66.exe?
Community
Member reviews and reports for this exact file hash.