Is Liminal Memory.exe safe?
Unsigned 640 kB PE with two low-trust detections and direct-IP traffic observed in sandbox.
Two engines flagged the file with generic machine-learning and heuristic labels; no tier-1 consensus or external-intel corroboration exists. The sample is unsigned, contacted external IPs without domains, and lacks any established signer or prevalence history that would clear it.
dcdd356539cfc8861b…dff74b333f70aaRecommended 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.
Two engines flagged the file with generic machine-learning and heuristic labels; no tier-1 consensus or external-intel corroboration exists. The sample is unsigned, contacted external IPs without domains, and lacks any established signer or prevalence history that would clear it.
The engine set shows only low-trust detections and no tier-1 agreement, yet the file remains unsigned and exhibits direct-IP network activity that triggered a heuristic rule. Medium prevalence and a 4-year age reduce the likelihood of a brand-new threat, but the absence of a completed host-reputation check and lack of RAG matches leave the risk unresolved. These mixed signals place the sample in the suspicious band rather than safe or malicious.
What We Detected
Two of 75 engines reported the sample: Malwarebytes (tier-2 ML.Anomalous.100%) and MaxSecure (low-trust Trojan.susgen). No tier-1 engine raised an alert, and no named malware family achieved consensus. The PE is unsigned and contains no packer evidence.
Threat Behavior
Sandbox execution showed auditpol commands and direct-IP connections to 20.99.132.105 and an IPv6 address; no domain names were resolved. The DirectIpC2 heuristic fired, but coverage of contacted-host reputation is incomplete.
What To Do Now
Do not run the file on production systems. Keep endpoint protection enabled and consider submitting the sample to additional sandboxes for deeper behavioral logging before any trust decision.
Where this verdict could be wrong1 caveat
- Malwarebytes tier2 ML.Anomalous.100% and MaxSecure low_trust Trojan label are generic heuristics; no named family consensus.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- No tier-1 detections
- Medium prevalence over 4 years
- No external-intel malicious hits
- Unsigned executable
- Direct-IP network traffic without domain
- Low-trust heuristic detections
Treat as untrusted; obtain further sandbox or dynamic-analysis results before allowing execution.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete2 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial3 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete1 signature or behavior rule 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
- 3MITRE ATT&CK techniques
- 15spawned processes
- 3network contacts
- 1filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Manipulated how the operating system loads code, which can redirect execution.
Note: Collects details about your system.
Note: Connected to 3 servers during sandbox analysis.
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
Liminal Memory.exe
dcdd356539cfc8861b9856133b52c73abbc97448a994cc75b2dff74b333f70aa
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
%SAMPLEPATH%\Liminal Memory.exe
02Isolated runtime analysis - ProcessObserved
Observed process
auditpol /set /subcategory:Security State Change /success:enable /failure:enable
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
a83f:8110:7200:5200:6500:7300:7400:7200
Contact observed during runtime.
04Isolated runtime analysis - Contacted hostObserved
20.99.132.105
Contact observed during runtime.
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.
- a83f:8110:7200:5200:6500:7300:7400:7200
- 20.99.132.105
- 192.168.0.14
- C:\Windows\System32\spp\store\2.0\cache\cache.dat
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 1rule hit recorded
- 2 / 75engines flagged
- 23sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
2 of 75 antivirus engines flagged the file, including Malwarebytes and MaxSecure.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 24 times from 23 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: Liminal Memory.exe — dcdd356539cfc8861b9856133b52c73abbc97448a994cc75b2dff74b333f70aa
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — %SAMPLEPATH%\Liminal Memory.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — auditpol /set /subcategory:Security State Change /success:enable /failure:enable
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Contacted host: a83f:8110:7200:5200:6500:7300:7400:7200 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
Contacted host: 20.99.132.105 — Contact observed during runtime.
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
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
The 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.
Evidencea83f:8110:7200:5200:6500:7300:7400:7200 · 20.99.132.105
2 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
- Liminal Memory.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 625.0 KB
- Last analyzed
- Aug 21, 2026, 2:42 PM UTC
dcdd356539cfc8861b9856133b52c73abbc97448a994cc75b2dff74b333f70aaSafety & 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 Liminal Memory.exe safe, or is it malware?
What is Liminal Memory.exe?
How many antivirus engines detected Liminal Memory.exe?
What should I do if I already ran Liminal Memory.exe?
How do I remove Liminal Memory.exe?
What is the SHA-256 hash of Liminal Memory.exe?
How up to date is this analysis of Liminal Memory.exe?
Community
Member reviews and reports for this exact file hash.