Is Space Invaders Setup.exe safe?
Unsigned installer shows LSASS access in one sandbox but zero engine detections over 7 years.
Zero of 74 engines flagged the file, yet the sandbox recorded LSASS memory access and five offensive MITRE techniques. The file is an unsigned 2019-era installer with medium prevalence and no corroborating malicious children or external-intel hits.
f7827ebc217bf245a7…ece0e0ffd29c4fRecommended 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.
Zero of 74 engines flagged the file, yet the sandbox recorded LSASS memory access and five offensive MITRE techniques. The file is an unsigned 2019-era installer with medium prevalence and no corroborating malicious children or external-intel hits.
The complete absence of detections across 17 tier-1 engines and 74 total engines is a strong clean signal. However, the sandbox recorded LSASS access (T1134) and four additional offensive techniques, triggering a credential-dumper heuristic. Because the file is unsigned and the single sandbox result is uncorroborated by any engine or dropped-child evidence, the sample sits in mixed-signals territory rather than a definitive clean or malicious verdict.
What We Detected
74 antivirus engines returned zero malicious or suspicious flags. The executable is unsigned and carries an installer hint in its filename. One sandbox recorded LSASS access plus five MITRE techniques normally associated with credential dumping or persistence.
Threat Behavior
The observed LSASS read is the only concrete suspicious action; no C2 traffic, no malicious dropped children, and no external-intel hits were found. The file has been submitted by 14 sources since 2019 with no community annotations.
What To Do Now
Do not run the installer in a privileged context. Keep endpoint protection enabled. If the software is required, obtain it from the original publisher and verify its digital signature before execution.
Where this verdict could be wrong1 caveat
- Sandbox observed LSASS access (T1134) but no tier-1 engine detections and no malicious dropped children; single-sandbox result may be a false positive or installer artifact.
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 74 engines
- No malicious dropped children
- Medium long-term prevalence with no recent complaints
- Unsigned executable
- Sandbox observed LSASS access
- Five offensive MITRE techniques logged
Treat as untrusted until a signed copy from the original publisher can be obtained; keep all security software active.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
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
- 35MITRE ATT&CK techniques
- 15spawned processes
- 0network contacts
- 40filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Created or modified a scheduled task, which can provide persistence.
High concern: Used an input-capture technique that can record credentials or keystrokes.
High concern: Used removable-media replication behaviour that can spread files between devices.
High concern: Created or modified a system service, which can keep code running.
High concern: Changed an auto-start location that can make code run after sign-in or restart.
High concern: Attempted to impair or bypass security controls.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
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
Space Invaders Setup.exe
f7827ebc217bf245a712e230a95971ff0af4b65a4813906803ece0e0ffd29c4f
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
holder0.aiph
C:\Users\<USER>\AppData\Roaming\Taito\Space Invaders 1.0.0\install\holder0.aiph
04Isolated runtime analysis - Written fileObserved
Space Invaders.msi
C:\Users\<USER>\AppData\Roaming\Taito\Space Invaders 1.0.0\install\Space Invaders.msi
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.
- C:\Users\<USER>\AppData\Roaming\Taito\Space Invaders 1.0.0\install\holder0.aiph
- C:\Users\<USER>\AppData\Roaming\Taito\Space Invaders 1.0.0\install\Space Invaders.msi
- C:\Users\<USER>\AppData\Local\Temp\shiE86C.tmp
- C:\Users\<USER>\AppData\Roaming\Taito\Space Invaders 1.0.0\install\Space Invaders1.cab
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.log
- C:\Users\<USER>\AppData\Roaming\Taito\Space Invaders 1.0.0\install\holder0.aiph
- C:\Windows\Tasks\C__Users_<USER>_Desktop_software.exe.job
- C:\Users\<USER>\AppData\Roaming\Taito\Space Invaders 1.0.0\install\Space Invaders.msi
- C:\Users\<USER>\AppData\Roaming\Taito\Space Invaders 1.0.0\install\Space Invaders1.cab
- C:\Users\<USER>\AppData\Roaming\Taito\Space Invaders 1.0.0\install
- Global\OneSettingQueryMutex+compat+encapsulation
- Global\_MSIExecute
- ZonesCounterMutex
- ZonesCacheCounterMutex
- ZonesLockedCacheCounterMutex
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- fcfc920b5af8d4384515…e362b7Never scannednever seen before
- d94f907cd1acd7cd4250…2dfffbNever scannednever seen before
- ba23b62cb0cee5d3d042…fb3854Never scannednever seen before
- 92a7e28859fc21992161…6a8107Never scannednever seen before
- 5a23037eb75bb1916d7e…cd3e5aNever scannednever seen before
- 0768c0a9d417cfe9874c…e192e4Never scannednever seen before
- 9c1e1067ffe17ebdfa3b…cbe162Never scannednever seen before
- 16a19763520bc5acfa82…a4042fNever scannednever seen before
- 15fb0bda4e4644d5769b…aa49fbNever scannednever seen before
- 0c077009fce6cc93df07…8f198aNever 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.
- 1rule hit recorded
- 0 / 74engines flagged
- 14sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 74 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 15 times from 14 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: Space Invaders Setup.exe — f7827ebc217bf245a712e230a95971ff0af4b65a4813906803ece0e0ffd29c4f
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Users\<USER>\Desktop\software.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — C:\Windows\system32\services.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: holder0.aiph — C:\Users\<USER>\AppData\Roaming\Taito\Space Invaders 1.0.0\install\holder0.aiph
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Space Invaders.msi — C:\Users\<USER>\AppData\Roaming\Taito\Space Invaders 1.0.0\install\Space Invaders.msi
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.
0 of 74 engines flagged this file
View all 74 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
- Space Invaders Setup.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 7.5 MB
- Last analyzed
- Aug 30, 2026, 10:17 AM UTC
f7827ebc217bf245a712e230a95971ff0af4b65a4813906803ece0e0ffd29c4fSafety & 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 Space Invaders Setup.exe safe, or is it malware?
What is Space Invaders Setup.exe?
How many antivirus engines detected Space Invaders Setup.exe?
I already downloaded and installed Space Invaders Setup.exe — what should I do?
How do I remove Space Invaders Setup.exe?
What is the SHA-256 hash of Space Invaders Setup.exe?
How up to date is this analysis of Space Invaders Setup.exe?
Community
Member reviews and reports for this exact file hash.