Is AutoKeyPresser.msi safe?
No antivirus engine detected the installer, but its unsigned origin and isolated T1055 and LSASS-related runtime signals warrant caution pending publisher verification.
All 75 antivirus engines avoided flagging this installer, including the participating tier-1 products, and the completed sandbox run did not issue a malware finding. However, the unsigned package produced possible process-injection and LSASS-related signals, while its direct IP contact lacks a completed reputation check.
687d859a43af153f16…3ccc9430436957Recommended 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.
All 75 antivirus engines avoided flagging this installer, including the participating tier-1 products, and the completed sandbox run did not issue a malware finding. However, the unsigned package produced possible process-injection and LSASS-related signals, while its direct IP contact lacks a completed reputation check.
The strongest reassuring evidence is that 0 of 75 engines reported a detection, with 16 tier-1 engines reporting no detection. One completed sandbox run also produced no malicious sandbox verdict and identified no malicious dropped child. Against that, the package is unsigned and has no publisher history to establish provenance. Runtime evidence maps activity to T1055 and raises an LSASS-related credential-access concern, although the saved process evidence does not conclusively prove injection or memory theft. The connection to 162.159.36.2 cannot be characterized because no complete contacted-host reputation result is available. These conflicting signals support caution rather than a definitive malware-family attribution.
What We Detected
No detections were reported by 75 antivirus engines, and 16 tier-1 engines reported no detection. The MSI is unsigned, however, so there is no verified publisher identity or established signer history supporting its origin.
Threat Behavior
One completed sandbox run did not issue a malicious verdict and no malicious dropped child was identified. The recorded activity nevertheless includes MITRE T1055 and an LSASS-related heuristic, which can be associated with process injection or credential access. The limited evidence shown does not conclusively establish either action. The installer also contacted 162.159.36.2 directly, but no complete host-reputation check is available for that address.
What To Do Now
Verify that the installer came from the developer's official release channel and compare its SHA-256 value, 687d859a43af153f16f0777061e5f6cb5c68374d77cc49382c3ccc9430436957, with a publisher-provided checksum. Keep endpoint protection enabled and avoid installing it on a sensitive system until its publisher and runtime purpose are confirmed.
Where this verdict could be wrong3 caveats
- The T1055 mapping and LSASS-related heuristic conflict with the complete absence of detections across 75 engines.
- The installer contacted 162.159.36.2 directly, but contactedHosts=null means the available evidence cannot establish whether that host was harmful.
- The sole sandbox verdict was clean, although one run may not expose delayed or conditional behavior.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0 of 75 antivirus engines reported a detection
- 16 tier-1 engines reported no detection
- The completed sandbox run did not issue a malicious verdict
- No malicious dropped child was identified
- No brand mismatch was detected
- Unsigned Windows Installer with no verified publisher identity
- Runtime mapping to MITRE T1055
- LSASS-related activity raised a credential-access heuristic
- Direct connection to 162.159.36.2 lacks a completed reputation check
- Only one completed sandbox observation
Obtain the MSI only from the developer's official channel and verify its SHA-256 checksum before use. Keep endpoint protection enabled and test it in an isolated environment if publisher verification is unavailable.
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
PartialIndependent reference checks were attempted but are incomplete.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 5MITRE ATT&CK techniques
- 9spawned processes
- 1network contacts
- 8filesystem & 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 removable-media replication behaviour that can spread files between devices.
Note: Reads your Windows user-account details.
Note: Collects details about your system.
Note: Connected to 1 server 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
AutoKeyPresser.msi
687d859a43af153f16f0777061e5f6cb5c68374d77cc49382c3ccc9430436957
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\setup.msi" /qb ACCEPTEULA=1 LicenseAccepted=1
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
Download-1.tmp
C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
04Isolated runtime analysis - Written fileObserved
MSIa5ae9.tmp
C:\MSIa5ae9.tmp
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:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
- C:\MSIa5ae9.tmp
- C:\Windows\Fonts
- C:\Windows\system32\catroot
- C:\Windows\system32\catroot2
- C:\MSIa5ae9.tmp
- Global\_MSIExecute
- \BaseNamedObjects\Local\SM0:1008:304:WilStaging_02
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
- 23sources 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 24 times from 23 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: AutoKeyPresser.msi — 687d859a43af153f16f0777061e5f6cb5c68374d77cc49382c3ccc9430436957
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\setup.msi" /qb ACCEPTEULA=1 LicenseAccepted=1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\services.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Download-1.tmp — C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: MSIa5ae9.tmp — C:\MSIa5ae9.tmp
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.
Available reference checks returned no match, but at least one source was unavailable. This is not a clean result.
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
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- AutoKeyPresser.msi
- Format
- Windows Installer
- Code signing
- No verified publisher
- Size
- 14.8 MB
- Last analyzed
- Oct 3, 2026, 6:08 AM UTC
687d859a43af153f16f0777061e5f6cb5c68374d77cc49382c3ccc9430436957Safety & 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 AutoKeyPresser.msi safe, or is it malware?
What is AutoKeyPresser.msi?
How many antivirus engines detected AutoKeyPresser.msi?
What should I do if I already installed AutoKeyPresser.msi?
How do I remove AutoKeyPresser.msi?
What is the SHA-256 hash of AutoKeyPresser.msi?
How up to date is this analysis of AutoKeyPresser.msi?
Community
Member reviews and reports for this exact file hash.