Is aomei-onekey-recovery-1-7-1.exe safe?
Properly signed AOMEI recovery installer with zero engine detections and long clean prevalence history.
Zero of 75 engines flagged the file. It is signed by AOMEI International Network Limited and has been submitted 470 times since 2021 with no malicious detections. The observed MITRE techniques and direct-IP contacts are consistent with legitimate installer behaviour.
9719e1abde7fb8c6bb…59111a69572b08Recommended next actions
Before running
Run it only when it came from the developer's official site or another source you independently trust.
If you already ran it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
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. It is signed by AOMEI International Network Limited and has been submitted 470 times since 2021 with no malicious detections. The observed MITRE techniques and direct-IP contacts are consistent with legitimate installer behaviour.
The file shows a clean engine profile with 17 tier-1 engines reporting it harmless and no tier-1 malicious detections. It carries a valid signature from the vendor named in the filename. Prevalence data indicates it is common_old software with hundreds of prior submissions. While synthesis heuristics flagged process injection and direct-IP behaviour, these are typical of signed installers that extract components and register services. Similar imphash matches were unsigned files from unrelated families, providing no contradictory evidence against this signed sample.
What We Detected
75 engines scanned the sample; none returned malicious results. 17 tier-1 engines explicitly classified it as clean. The executable is signed and timestamped December 2021 by AOMEI International Network Limited. Sandbox execution showed typical installer activity: temporary file extraction, service registration, and network connections to content-delivery endpoints.
Threat Behavior
Four MITRE techniques (T1055, T1055.011, T1543.003, T1547.001) were observed along with direct-IP contacts. These behaviours occur in legitimate installers that unpack payloads and register recovery services. No malicious children were dropped, no C2 domains were contacted, and no sandbox flagged the sample as malicious.
What To Do Now
The file can be considered safe for use. Verify the digital signature in Windows before execution and download only from the official AOMEI website to ensure you have the authentic package.
Where this verdict could be wrong2 caveats
- If the AOMEI certificate were stolen, the clean engine results and long prevalence history would be misleading — however signerStats shows no prior malicious samples under this publisher.
- Direct-IP contacts and process injection techniques could indicate sophisticated malware, but these behaviours are also consistent with legitimate installer frameworks unpacking and registering services.
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 engine detections across 75 scanners
- Valid signature from AOMEI International Network Limited
- 470 prior submissions with clean reputation
- No malicious dropped children or sandbox verdicts
The evidence supports treating this as a legitimate AOMEI recovery tool. Run it only after confirming the digital signature matches the vendor.
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
Partial20 runtime contacts were observed without a completed reputation cross-check.
YARA
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
- 28MITRE ATT&CK techniques
- 15spawned processes
- 20network contacts
- 40filesystem & mutex artifacts
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
aomei-onekey-recovery-1-7-1.exe
9719e1abde7fb8c6bb8330d7ced83c7ed95bf5385b0280e5b059111a69572b08
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\file.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\is-K3H6D.tmp\file.tmp" /SL5="$30054,28098390,140800,C:\Users\<USER>\AppData\Local\Temp\file.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
996E.tmp
C:\Documents and Settings\Administrator\Local Settings\Temp\is-57SL4.tmp\996E.tmp
04Isolated runtime analysis - Written fileObserved
_shfoldr.dll
C:\Documents and Settings\Administrator\Local Settings\Temp\is-RMQJM.tmp\_isetup\_shfoldr.dll
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
23.40.197.184
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
209.197.3.8
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 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.
- 23.40.197.184
- 209.197.3.8
- 23.216.147.64
- 20.99.132.105
- 20.62.24.77
- 23.216.147.76
- 20.99.133.109
- a83f:8110:1a1a:1aff:1b1b:1bff:1b1b:1bff
- 23.216.147.62
- 20.99.184.37
- C:\Documents and Settings\Administrator\Local Settings\Temp\is-57SL4.tmp\996E.tmp
- C:\Documents and Settings\Administrator\Local Settings\Temp\is-RMQJM.tmp\_isetup\_shfoldr.dll
- C:\Documents and Settings\Administrator\Local Settings\Temp\is-RMQJM.tmp\OneKeyScriptDLL.dll
- C:\Documents and Settings\Administrator\Local Settings\Temp\is-A6G5N.tmp\996E.tmp
- C:\Documents and Settings\Administrator\Local Settings\Temp\is-KB9VA.tmp\_isetup\_shfoldr.dll
- C:\Users\<USER>\AppData\Local\Temp\is-K3H6D.tmp\Amok.dll
- C:\Users\<USER>\AppData\Local\Temp\Amok.dll
- C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\Microsoft\Crypto\Keys\de7cf8a7901d2ad13e5c67c29e5d1662_cbbb49d6-b7ff-44ca-aba5-8a5e250d4d42
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERFCDE.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERFD99.tmp.csv
- Local\RstrMgr3887CAB8-533F-4C85-B0DC-3E5639F8D511
- Local\RstrMgr-3887CAB8-533F-4C85-B0DC-3E5639F8D511-Session0000
- Global\AmWebReg
- CTF.LBES.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Compart.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 4252ef0ec82de8b6634f…35e10eNever scannednever seen before
- bf83b3165deadcfa3d7b…2ad571Never scannednever seen before
- 9884e9d1b4f8a873ccbd…360d87Never scannednever seen before
- a4c86fc4836ac728d7bd…95fd81Never scannednever seen before
- 0b16ad93ee38243d72ff…c8d531Never scannednever seen before
- 6e9dbd60bd5cb014044d…6d964aNever scannednever seen before
- 71dacebe04e1b24f9af6…8edffeNever scannednever seen before
- 79d16ec8641ebe680ff0…0dc705Never scannednever seen before
- 060c82c2e04d22fb40a3…939898Never scannednever seen before
- 5612260cdb8a75f601ed…e1b1e7Never 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
- 0 / 75engines flagged
- 246sources 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 75 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 246 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
The file has a valid code signature from AOMEI International Network Limited.
ProvenanceObservedSourceCode-signing metadataObserved at - 04
Scanned file: aomei-onekey-recovery-1-7-1.exe — 9719e1abde7fb8c6bb8330d7ced83c7ed95bf5385b0280e5b059111a69572b08
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\AppData\Local\Temp\file.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\<USER>\AppData\Local\Temp\is-K3H6D.tmp\file.tmp" /SL5="$30054,28098390,140800,C:\Users\<USER>\AppData\Local\Temp\file.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: 996E.tmp — C:\Documents and Settings\Administrator\Local Settings\Temp\is-57SL4.tmp\996E.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: _shfoldr.dll — C:\Documents and Settings\Administrator\Local Settings\Temp\is-RMQJM.tmp\_isetup\_shfoldr.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 23.40.197.184 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 209.197.3.8 — 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.
MITRE T1055 (Process Injection) observed — CreateRemoteThread / APC / reflective-DLL injection. The payload is being smuggled into a legitimate process to bypass AV hooks.
Evidence"C:\Users\<USER>\AppData\Local\Temp\file.exe"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.
Evidence23.40.197.184 · 209.197.3.8 · 23.216.147.64
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
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Fingerprint and provenance
- File name
- aomei-onekey-recovery-1-7-1.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: AOMEI International Network Limited
- Size
- 27.3 MB
- Last analyzed
- Jul 3, 2026, 10:17 AM UTC
9719e1abde7fb8c6bb8330d7ced83c7ed95bf5385b0280e5b059111a69572b08Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Run it only when it came from the developer's official site or another source you independently trust.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is aomei-onekey-recovery-1-7-1.exe safe?
What is aomei-onekey-recovery-1-7-1.exe?
How many antivirus engines detected aomei-onekey-recovery-1-7-1.exe?
Is aomei-onekey-recovery-1-7-1.exe digitally signed?
What is the SHA-256 hash of aomei-onekey-recovery-1-7-1.exe?
Is it safe to run aomei-onekey-recovery-1-7-1.exe?
How up to date is this analysis of aomei-onekey-recovery-1-7-1.exe?
Community
Member reviews and reports for this exact file hash.