Is driftaline-installer-v1.7.exe safe?
A lone generic detection conflicts with unsigned status and sandbox mappings for process injection, LSASS access, data destruction, and file-impact behavior.
Only 1 of 75 engines flagged this installer, with no high-trust detection or named family. However, the unsigned executable produced structured runtime indicators involving process injection and LSASS targeting, alongside T1485 and T1486, so it should not be run without stronger provenance and isolated testing.
52843c8d893571bca8…7d92632b2582cdRecommended 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.
Only 1 of 75 engines flagged this installer, with no high-trust detection or named family. However, the unsigned executable produced structured runtime indicators involving process injection and LSASS targeting, alongside T1485 and T1486, so it should not be run without stronger provenance and isolated testing.
The antivirus result is weak: DeepInstinct alone flagged the sample, while no tier-1 engine identified malware or agreed on a family. The executable is unsigned and has no established publisher history, removing an important trust signal for an installer. One sandbox run received a clean summary, but its structured evidence mapped possible process injection, LSASS targeting, data destruction, and file-impact behavior. No dropped child was identified as malicious, although all ten child verdicts remain unknown, and no complete contacted-host reputation check is available. Similar-file history trends concerning, but those records share only an imphash without a matching signer and may reflect a common installer framework. These conflicts support caution rather than a definitive malware-family attribution.
What We Detected
DeepInstinct was the only detector among 75 engines, and none of the tier-1 engines reported a malicious result or family consensus. The executable is unsigned and has no historical signer record, so its publisher cannot be authenticated.
Threat Behavior
One completed sandbox run mapped T1055 process injection, T1485 data destruction, and T1486 file-impact behavior. A separate heuristic also reports process activity targeting LSASS, which can indicate credential-access behavior. The sandbox summary itself was clean, no persistence indicators were recorded, and no dropped child was identified as malicious; however, all ten child verdicts remain unknown. No complete contacted-host reputation result is available, and contaminated free-text sandbox material was ignored.
What To Do Now
Do not execute the installer on a production system until its origin and hash are confirmed through the developer's official release channel. Keep endpoint protection enabled and, if analysis is necessary, use an isolated disposable environment with monitoring.
Where this verdict could be wrong4 caveats
- Only 1/75 engines flagged the file, and BitDefender, Kaspersky, ESET-NOD32, Fortinet, and other tier-1 engines reported no detection.
- behaviour.sandboxVerdicts[0].verdict=clean and behaviour.hasMaliciousSandboxVerdict=false, although the structured activity mappings remain concerning.
- droppedChildren.hasMaliciousChild=false, but all 10 inspected children have unknown verdicts rather than affirmative benign results.
- externalIntel.yaraify.ruleCount=0 and externalIntel.malwareBazaar.hit=false provide no researcher-curated corroboration.
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 detected the sample
- engines.tier1Malicious=0 with no family consensus
- behaviour.hasMaliciousSandboxVerdict=false
- droppedChildren.hasMaliciousChild=false
- peAnalysis.likelyPacked=false and highEntropyCode=false
- Unsigned Win32 installer with no authenticated publisher history
- Structured sandbox mapping to T1055 process injection
- Heuristic evidence of LSASS-targeting activity
- Runtime mappings include T1485 and T1486
- No complete contacted-host reputation result is available
- All 10 dropped-child verdicts remain unknown
Verify the SHA-256 through the developer's official release channel and avoid running it if that provenance cannot be established. Keep endpoint protection enabled and use an isolated disposable system for any necessary testing.
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
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
Complete2 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
- 11MITRE ATT&CK techniques
- 13spawned processes
- 0network 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.
High concern: Encrypted files or data, behaviour commonly associated with ransomware.
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.
Moderate concern: Checked the environment for virtualisation or analysis tools.
Note: Reads your Windows user-account details.
Note: Collects details about your system.
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
driftaline-installer-v1.7.exe
52843c8d893571bca8662044117859cbce081c633e5dbed7e47d92632b2582cd
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\driftaline-installer-v1.7.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\is-RI7V7VL1N2.tmp\driftaline-installer-v1.7.tmp" /SL5="$17006E,47899244,887296,C:\Users\<USER>\Desktop\driftaline-installer-v1.7.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
driftaline-installer-v1.7.tmp
C:\Users\<USER>\AppData\Local\Temp\is-RI7V7VL1N2.tmp\driftaline-installer-v1.7.tmp
04Isolated runtime analysis - Written fileObserved
_setup64.tmp
C:\Users\<USER>\AppData\Local\Temp\is-3CL4X38UQL.tmp\_isetup\_setup64.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
5 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.
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\RestartManager\Session0000\RegFiles0000
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\RestartManager\Session0000\RegFilesHash
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{01D25B16-0DB0-4CA1-97BB-297CF3A47331}_is1\Inno Setup: Setup Version
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{01D25B16-0DB0-4CA1-97BB-297CF3A47331}_is1\Inno Setup: App Path
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{01D25B16-0DB0-4CA1-97BB-297CF3A47331}_is1\InstallLocation
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{01D25B16-0DB0-4CA1-97BB-297CF3A47331}_is1\Inno Setup: Icon Group
- C:\Users\<USER>\AppData\Local\Temp\is-RI7V7VL1N2.tmp\driftaline-installer-v1.7.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-3CL4X38UQL.tmp\_isetup\_setup64.tmp
- C:\Users\<USER>\AppData\Local\Microsoft\Windows\Explorer\iconcache_idx.db
- C:\Users\<USER>\AppData\Local\Microsoft\Windows\Explorer\iconcache_256.db
- C:\Users\<USER>\AppData\Local\Microsoft\Windows\Explorer\iconcache_48.db
- C:\Users\<USER>\AppData\Local\Programs\DriftAline\is-UR0NLOMOQG.tmp
- C:\Users\<USER>\AppData\Local\Programs\DriftAline\is-WPA8EGSRHF.tmp
- C:\Users\<USER>\AppData\Local\Programs\DriftAline\is-KNZ508B170.tmp
- C:\Users\<USER>\AppData\Local\Programs\DriftAline\is-WMUBRU8QYZ.tmp
- C:\Users\<USER>\AppData\Local\Programs\DriftAline\DriftAline.exe
- cversions.3.m
- \Sessions\1\BaseNamedObjects\Local\RstrMgr3887CAB8-533F-4C85-B0DC-3E5639F8D511
- \Sessions\1\BaseNamedObjects\Local\RstrMgr-3887CAB8-533F-4C85-B0DC-3E5639F8D511-Session0000
- \Sessions\1\BaseNamedObjects\Global\C::Users:user:AppData:Local:Microsoft:Windows:Explorer:iconcache_idx.db!rwWriterMutex
- \Sessions\1\BaseNamedObjects\Global\C::Users:user:AppData:Local:Microsoft:Windows:Explorer:iconcache_16.db!dfMaintainer
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- c64cc82d5637aab901c3…9aeadeNever scannednever seen before
- aebea1cded11cabb53f6…61e5d5Never scannednever seen before
- 42ef18c42fe06709f3c8…ddfca0Never scannednever seen before
- 9603fdfd2b4bd75b3574…6c004aNever scannednever seen before
- ba7d8c2cffb3b38459e9…9c590dNever scannednever seen before
- 3a99322cbfd7fbf4bf7f…1957a5Never scannednever seen before
- b82327cbf824fdf633c2…a77fa4Never scannednever seen before
- 3c081097dca98557b27c…bc5b21Never scannednever seen before
- 30035484c81590976627…cab707Never scannednever seen before
- 557059c8c0488f9f9681…7d59a7Never 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.
- 2rule hits recorded
- 1 / 75engines flagged
- 88sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
1 of 75 antivirus engines flagged the file, including DeepInstinct.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 91 times from 88 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: driftaline-installer-v1.7.exe — 52843c8d893571bca8662044117859cbce081c633e5dbed7e47d92632b2582cd
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\driftaline-installer-v1.7.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\<USER>\AppData\Local\Temp\is-RI7V7VL1N2.tmp\driftaline-installer-v1.7.tmp" /SL5="$17006E,47899244,887296,C:\Users\<USER>\Desktop\driftaline-installer-v1.7.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: driftaline-installer-v1.7.tmp — C:\Users\<USER>\AppData\Local\Temp\is-RI7V7VL1N2.tmp\driftaline-installer-v1.7.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: _setup64.tmp — C:\Users\<USER>\AppData\Local\Temp\is-3CL4X38UQL.tmp\_isetup\_setup64.tmp
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\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.exe
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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- driftaline-installer-v1.7.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 46.9 MB
- Last analyzed
- Oct 7, 2026, 4:14 PM UTC
52843c8d893571bca8662044117859cbce081c633e5dbed7e47d92632b2582cdSafety & 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 driftaline-installer-v1.7.exe safe, or is it malware?
What is driftaline-installer-v1.7.exe?
How many antivirus engines detected driftaline-installer-v1.7.exe?
What should I do if I already installed driftaline-installer-v1.7.exe?
How do I remove driftaline-installer-v1.7.exe?
What is the SHA-256 hash of driftaline-installer-v1.7.exe?
How up to date is this analysis of driftaline-installer-v1.7.exe?
Community
Member reviews and reports for this exact file hash.