Is VyxxnnDLCUnlockerSetup.exe safe?
A lone generic detection is outweighed by tier-1 silence, but unsigned code and observed T1055 and LSASS-related activity warrant isolation and further verification.
Only 1 of 75 engines flagged this installer, and none of the 17 tier-1 engines detected it. However, the unsigned executable produced runtime evidence associated with process injection and LSASS access, so it should not be run on a normal system without source verification and deeper analysis.
e2c6ed3d3f97c5166a…363978641067e6Recommended 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.
Only 1 of 75 engines flagged this installer, and none of the 17 tier-1 engines detected it. However, the unsigned executable produced runtime evidence associated with process injection and LSASS access, so it should not be run on a normal system without source verification and deeper analysis.
The antivirus result is weak: DeepInstinct alone flagged the sample, while all 17 tier-1 engines reported no detection and no malware family consensus exists. Runtime evidence nevertheless maps activity to T1055 Process Injection and records LSASS-related process activity, which is unusual for an installer. The file is unsigned and has no established signer history, leaving no authenticated publisher evidence to explain those actions. One sandbox did not issue a malicious verdict, and neither inspected child was identified as malicious, although both child verdicts remain unresolved. No complete contacted-host reputation result is available, and the prior imphash matches are limited by absent signer co-matches. These conflicting signals support caution rather than a definitive malware-family attribution.
What We Detected
DeepInstinct was the only engine to flag the file: 1 of 75 engines overall. None of the 17 tier-1 engines detected it, and no named malware family reached consensus. The executable is unsigned and has no verified publisher history.
Threat Behavior
The completed sandbox run recorded evidence mapped to MITRE T1055 Process Injection and LSASS-related process activity. Those actions can be associated with credential access or code injection, although the available evidence does not establish the exact method or intent. The sandbox itself did not return a malicious verdict, no persistence indicators were saved, and two dropped children were not identified as malicious; however, both child verdicts remain unknown. No complete contacted-host reputation result is available.
What To Do Now
Do not run this installer on a production or personal system until its origin and publisher can be independently verified. Keep endpoint protection enabled, quarantine the file, and obtain a fresh copy from the software publisher's official release channel if the program is expected.
Where this verdict could be wrong5 caveats
- Only 1/75 engines detected the sample, and all 17 tier-1 engines reported no detection.
- behaviour.hasMaliciousSandboxVerdict=false, with the sole saved sandbox verdict marked clean.
- droppedChildren.hasMaliciousChild=false after two children were inspected, although both child verdicts remain unknown.
- prevalence records 282 submitters and 339 submissions, so the sample is not exceptionally rare.
- peAnalysis.highEntropyCode=false and peAnalysis.likelyPacked=false provide no static packing signal.
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 the sample.
- All 17 tier-1 engines reported no detection.
- The completed sandbox did not issue a malicious verdict.
- droppedChildren.hasMaliciousChild=false.
- peAnalysis.likelyPacked=false and highEntropyCode=false.
- MITRE T1055 Process Injection was mapped from saved runtime evidence.
- LSASS-related activity triggered MalwareTips.Synth.CredentialDumper.
- The Win32 executable is unsigned and has no signer history.
- Both dropped-child verdicts remain unknown.
- No complete contacted-host reputation cross-check is available.
- Prior imphash matches include four suspicious and one malicious decision, though they lack signer co-matches.
Quarantine the file and verify its hash and download source with the legitimate publisher before use. Keep antivirus and endpoint protection enabled; if verification is impossible, remove it.
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
- 7MITRE ATT&CK techniques
- 12spawned processes
- 0network contacts
- 20filesystem & 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: Communicated over a common application protocol; malware can use this for command-and-control.
Note: Reads your Windows user-account details.
Note: Collects details about your system.
Note: Loads extra code modules 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
VyxxnnDLCUnlockerSetup.exe
e2c6ed3d3f97c5166a83422da8bd2220010902f05f0cfa4cdc363978641067e6
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\VyxxnnDLCUnlockerSetup.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\is-DENE49G31Y.tmp\VyxxnnDLCUnlockerSetup.tmp" /SL5="$40168,39874037,893952,C:\Users\<USER>\Desktop\VyxxnnDLCUnlockerSetup.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
VyxxnnDLCUnlockerSetup.tmp
C:\Users\<USER>\AppData\Local\Temp\is-DENE49G31Y.tmp\VyxxnnDLCUnlockerSetup.tmp
04Isolated runtime analysis - Written fileObserved
Download-1.tmp
C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.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_USERS\S-1-5-21-575823232-3065301323-1442773979-1000\Software\Microsoft\RestartManager\Session0000\Owner
- HKEY_USERS\S-1-5-21-575823232-3065301323-1442773979-1000\Software\Microsoft\RestartManager\Session0000\Sequence
- HKEY_USERS\S-1-5-21-575823232-3065301323-1442773979-1000\Software\Microsoft\RestartManager\Session0000\SessionHash
- Software\Microsoft\RestartManager\Session0000\Owner
- Software\Microsoft\RestartManager\Session0000\SessionHash
- Software\Microsoft\RestartManager\Session0000\Sequence
- C:\Users\<USER>\AppData\Local\Temp\is-DENE49G31Y.tmp\VyxxnnDLCUnlockerSetup.tmp
- C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-0CJIHIZ4PO.tmp\VyxxnnDLCUnlockerSetup.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-EI49ITLZCI.tmp\_isetup\_setup64.tmp
- C:\Users\user\AppData\Local\Microsoft\Windows\Explorer
- \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
- \Sessions\1\BaseNamedObjects\Global\C::Users:user:AppData:Local:Microsoft:Windows:Explorer:iconcache_32.db!dfMaintainer
Files this sample writes at runtime
This file drops 2 children at runtime. None are currently flagged malicious in our cache.
- e94e9a55db3d5bc636d2…909f84Never scannednever seen before
- 388a796580234efc95f3…136f95Never 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
- 282sources 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 339 times from 282 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: VyxxnnDLCUnlockerSetup.exe — e2c6ed3d3f97c5166a83422da8bd2220010902f05f0cfa4cdc363978641067e6
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\VyxxnnDLCUnlockerSetup.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\<USER>\AppData\Local\Temp\is-DENE49G31Y.tmp\VyxxnnDLCUnlockerSetup.tmp" /SL5="$40168,39874037,893952,C:\Users\<USER>\Desktop\VyxxnnDLCUnlockerSetup.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: VyxxnnDLCUnlockerSetup.tmp — C:\Users\<USER>\AppData\Local\Temp\is-DENE49G31Y.tmp\VyxxnnDLCUnlockerSetup.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: Download-1.tmp — C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.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\system32\DllHost.exe /Processid:{F32D97DF-E3E5-4CB9-9E3E-0EB5B4E49801}Sandbox 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
- VyxxnnDLCUnlockerSetup.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 39.2 MB
- Last analyzed
- Sep 24, 2026, 10:18 AM UTC
e2c6ed3d3f97c5166a83422da8bd2220010902f05f0cfa4cdc363978641067e6Safety & 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 VyxxnnDLCUnlockerSetup.exe safe, or is it malware?
What is VyxxnnDLCUnlockerSetup.exe?
How many antivirus engines detected VyxxnnDLCUnlockerSetup.exe?
I already downloaded and ran VyxxnnDLCUnlockerSetup.exe — what should I do?
How do I remove VyxxnnDLCUnlockerSetup.exe?
What is the SHA-256 hash of VyxxnnDLCUnlockerSetup.exe?
How up to date is this analysis of VyxxnnDLCUnlockerSetup.exe?
Community
Member reviews and reports for this exact file hash.