Is lottylife.exe safe?
Unsigned executable shows sandbox evidence of process injection and LSASS access with no AV detections.
Zero of 75 engines flagged the file, yet sandbox behaviour includes T1055 process injection and LSASS targeting. The file is unsigned and prevalence is only medium, leaving mixed signals that warrant caution.
3deaa56853238969ca…49a67c587d1251Recommended 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.
Zero of 75 engines flagged the file, yet sandbox behaviour includes T1055 process injection and LSASS targeting. The file is unsigned and prevalence is only medium, leaving mixed signals that warrant caution.
The complete absence of engine detections rules out a clear malicious consensus, but the sandbox recorded two offensive MITRE techniques and two high-severity heuristics that map to credential-dumping and injection behaviour. Because the sample is unsigned and no prior similar-hash verdicts exist, the evidence is not strong enough for a safe classification. The single observed IP lacks a completed host-reputation check, adding another unknown. Overall the file sits in a borderline zone that requires further scrutiny or detonation in a controlled environment.
What We Detected
75 antivirus engines returned zero malicious or suspicious flags. The PE is unsigned and first appeared today. Sandbox execution recorded process-injection (T1055) and elevation (T1548) techniques plus direct-IP contact to 162.159.36.2.
Threat Behavior
Two heuristics fired at high and medium severity: one mapping LSASS access to credential-dumping patterns, another mapping injected code into svchost.exe. No dropped children, persistence mechanisms, or external-intel hits were observed.
What To Do Now
Do not run the file on production systems. Submit it to additional sandboxes or allow-list it only after manual review confirms the observed behaviour is expected for its stated purpose.
Where this verdict could be wrong1 caveat
- contactedHosts is null — no complete host-reputation result available for the observed IP 162.159.36.2
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Zero detections across 75 engines
- Medium prevalence with 16 submitters
- Unsigned executable
- Sandbox shows T1055 process injection
- Sandbox shows LSASS access (T1548)
- Direct-IP contact with no domain (possible C2)
Treat the sample as untrusted; keep endpoint protection enabled and perform additional behavioural analysis before any execution.
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 runtime contact was observed without a completed reputation cross-check.
YARA
Complete3 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
- 13MITRE ATT&CK techniques
- 10spawned processes
- 1network contacts
- 14filesystem & 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: Used an input-capture technique that can record credentials or keystrokes.
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: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Scans through your files and folders.
Moderate concern: Checked the environment for virtualisation or analysis tools.
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
lottylife.exe
3deaa56853238969cae2078c9ec7c7ac599e0f5ce83d10f50a49a67c587d1251
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\software.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\services.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Caches
C:\Users\user\AppData\Local\Microsoft\Windows\Caches
04Isolated runtime analysis - Written fileObserved
Explorer
C:\Users\user\AppData\Local\Microsoft\Windows\Explorer
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\Microsoft\Windows\Caches
- C:\Users\user\AppData\Local\Microsoft\Windows\Explorer
- C:\Users\user\AppData\Local\Temp\GameMaker.1787713589\
- C:\Users\user\AppData\Roaming\Microsoft\Windows\Recent\AutomaticDestinations
- Local\Shell.CMruPidlList
- Local\SessionImmersiveColorMutex
- Local\Mutexf01b4d95cf55d32a.automaticDestinations-ms
- Global\OneSettingQueryMutex+compat+encapsulation
- \Sessions\1\BaseNamedObjects\Global\C::Users:user:AppData:Local:Microsoft:Windows:Explorer:iconcache_idx.db!rwWriterMutex
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 3rule hits recorded
- 0 / 75engines flagged
- 16sources 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
0 of 75 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 21 times from 16 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: lottylife.exe — 3deaa56853238969cae2078c9ec7c7ac599e0f5ce83d10f50a49a67c587d1251
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\software.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\services.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Caches — C:\Users\user\AppData\Local\Microsoft\Windows\Caches
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: Explorer — C:\Users\user\AppData\Local\Microsoft\Windows\Explorer
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.
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\svchost.exe -k NetworkService -pSandbox 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
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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- lottylife.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 13.2 MB
- Last analyzed
- Aug 26, 2026, 6:29 AM UTC
3deaa56853238969cae2078c9ec7c7ac599e0f5ce83d10f50a49a67c587d1251Safety & 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 lottylife.exe safe, or is it malware?
What is lottylife.exe?
How many antivirus engines detected lottylife.exe?
I already downloaded and ran lottylife.exe — what should I do?
How do I remove lottylife.exe?
What is the SHA-256 hash of lottylife.exe?
How up to date is this analysis of lottylife.exe?
Community
Member reviews and reports for this exact file hash.