Is iPhoneUnlocker.exe safe?
75 of 75 engines report clean, signed installer with no malicious sandbox behaviour observed.
Zero detections across 75 engines, verified digital signature, and no malicious sandbox or child-file findings support a clean classification. The signer lacks prior history in our records, but the absence of any malicious signals outweighs that gap.
e02bdabc21bd027d27…b2f8bc8fa6c0caRecommended 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 detections across 75 engines, verified digital signature, and no malicious sandbox or child-file findings support a clean classification. The signer lacks prior history in our records, but the absence of any malicious signals outweighs that gap.
The file triggered no engine detections and no tier-1 consensus. Sandbox execution produced only ambient techniques and no malicious verdict. Two dropped children were inspected and found clean. While the signer has no established history, the combination of zero detections, verified signature, and medium prevalence aligns with prevalent commodity software rather than malware.
What We Detected
75 engines scanned the sample; none returned malicious or suspicious labels. The executable is digitally signed by Shenzhen Tengke Technology Co. and the signature verified successfully. Sandbox analysis recorded two ambient MITRE techniques (T1033, T1036) but no offensive techniques and no malicious verdict.
Threat Behavior
No domains, IPs, or URLs were contacted. Two child files were dropped; both were inspected and carried no malicious verdicts. No persistence mechanisms or registry modifications were observed.
What To Do Now
The file can be executed in a standard environment. Keep endpoint protection enabled as a general precaution.
Where this verdict could be wrong2 caveats
- signerStats.found=false — no historical samples for 'Shenzhen Tengke Technology Co.' to establish trust baseline.
- similarHashes returned 2 'suspicious' verdicts on imphash matches (matchKind=imphash, signerCoMatch=false) — framework collision possible but not decisive.
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
- Verified digital signature present
- No malicious sandbox verdict or dropped malicious children
The evidence supports treating the file as safe for normal use; continue running current endpoint protection.
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
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
CompleteRule evaluation completed with no recorded matches.
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
- 2MITRE ATT&CK techniques
- 3spawned processes
- 0network contacts
- 13filesystem & 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
iPhoneUnlocker.exe
e02bdabc21bd027d272dcd4ac1bceb870100c38c19103f2374b2f8bc8fa6c0ca
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
C:\Users\<USER>\AppData\Local\Temp\is-HBOST.tmp\iPhoneUnlocker.tmp /SL5=$4015C,109353316,834048,C:\Users\<USER>\Downloads\iPhoneUnlocker.exe
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\user\Desktop\iPhoneUnlocker.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
iPhoneUnlocker.tmp
C:\Users\<USER>\AppData\Local\Temp\is-HBOST.tmp\iPhoneUnlocker.tmp
04Isolated runtime analysis - Written fileObserved
_setup64.tmp
C:\Users\<USER>\AppData\Local\Temp\is-F2RBS.tmp\_isetup\_setup64.tmp
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\Local\Temp\is-HBOST.tmp\iPhoneUnlocker.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-F2RBS.tmp\_isetup\_setup64.tmp
- C:\Windows\System32\Tasks\Microsoft\Windows\Application Experience\Microsoft Compatibility Appraiser
- C:\Users\user\AppData\Local\Programs
- C:\Users\user\AppData\Local\Programs\Common
- \Sessions\1\BaseNamedObjects\Local\RstrMgr3887CAB8-533F-4C85-B0DC-3E5639F8D511
- \Sessions\1\BaseNamedObjects\Local\RstrMgr-3887CAB8-533F-4C85-B0DC-3E5639F8D511-Session0000
Files this sample writes at runtime
This file drops 2 children at runtime. None are currently flagged malicious in our cache.
- 762c7b383c7973fcd782…fc11c9Never scannednever seen before
- 388a796580234efc95f3…136f95Never 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.
- 0rule hits recorded
- 0 / 75engines flagged
- 43sources 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 file has a valid code signature from Shenzhen Tengke Technology Co..
ProvenanceObservedSourceCode-signing metadataObserved at - 03
The hash has been submitted 45 times from 43 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: iPhoneUnlocker.exe — e02bdabc21bd027d272dcd4ac1bceb870100c38c19103f2374b2f8bc8fa6c0ca
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — C:\Users\<USER>\AppData\Local\Temp\is-HBOST.tmp\iPhoneUnlocker.tmp /SL5=$4015C,109353316,834048,C:\Users\<USER>\Downloads\iPhoneUnlocker.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\user\Desktop\iPhoneUnlocker.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: iPhoneUnlocker.tmp — C:\Users\<USER>\AppData\Local\Temp\is-HBOST.tmp\iPhoneUnlocker.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: _setup64.tmp — C:\Users\<USER>\AppData\Local\Temp\is-F2RBS.tmp\_isetup\_setup64.tmp
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.
YARA rules
No matchesThe rule pass completed without a saved public match.
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
- iPhoneUnlocker.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: Shenzhen Tengke Technology Co.
- Size
- 105.2 MB
- Last analyzed
- Aug 25, 2026, 1:16 AM UTC
e02bdabc21bd027d272dcd4ac1bceb870100c38c19103f2374b2f8bc8fa6c0caSafety & 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 iPhoneUnlocker.exe safe?
What is iPhoneUnlocker.exe?
How many antivirus engines detected iPhoneUnlocker.exe?
Is iPhoneUnlocker.exe digitally signed?
What is the SHA-256 hash of iPhoneUnlocker.exe?
Is it safe to run iPhoneUnlocker.exe?
How up to date is this analysis of iPhoneUnlocker.exe?
Community
Member reviews and reports for this exact file hash.