File scan report
Verdict Suspicious
Is unlocker- setup (1). exe safe? Treat it as suspicious.
Installer for a file-unlocking utility that 16 of the 71 antivirus engines that checked it flag, several major antivirus engines naming a vulnerable driver or unwanted…
Read the whole reasonShow less
Why Suspicious? 16 antivirus engines flag it and one of our detection rules matched it.
Moderate evidence · More than one sign points to a problem, but nothing confirms it is harmful.
If it came from a link, an attachment or a stranger, delete it.
What to do now4 steps
Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.
What to do
Don't install it unless you're sure where it came from.
Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.
If you can't confirm where it came from, delete it. If you need the program, download it again from the publisher's own website.
If you already installed it
Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.
Not sure what to do?
Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
16 of 71 flagged
- Flagged 16
- No detection 55
- No result 4
- Code signing ORANGE VIEW LIMITED
- Test run Completed
- First seen 5mo ago
Chapter 02
Why we think so
4 points against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
ESET labels its driver a potentially unsafe vulnerable driver, and Sophos and DrWeb call it an unwanted application, while other major detections use generic labels. The combined sandbox verdict was clean and the run simply installed the utility, but the signer has almost no history with us.
Six major antivirus engines detections, from at least four independent scan engines, prevent treating this as a clean file. The most specific labels describe a potentially unsafe vulnerable driver and an unwanted application rather than a named malware family, and the remaining major labels are generic buckets. In the sandbox the installer placed program files, registered a shell extension and contacted its update server, and the combined sandbox verdict was clean with no injected process recorded. The valid signature belongs to a publisher with only one prior sample in our records, so it adds little trust. Taken together, this looks like a legitimate-purpose tool carrying components that engines consider risky, not confirmed malware.
What We Detected
16 of the 71 antivirus engines that checked it flagged the file. ESET reports a potentially unsafe vulnerable driver, Sophos and DrWeb report a potentially unwanted application, and Avast, AVG, Avira, F-Secure and Trellix use generic malware labels. No malware family is agreed on by multiple major antivirus engines. The file was first seen on Apr 30, 2026 and has been submitted by about 1,900 sources.
Threat Behavior
The combined sandbox verdict was clean. The installer unpacked itself, installed the unlocker program and its libraries, registered a shell extension and contacted its vendor's update server. No complete contacted-host reputation result was available. Engines flag drivers like this because a vulnerable driver can be abused by other malware to gain kernel access.
What To Do Now
Install it only if you need a file-unlocking tool and obtained it from the developer's official site. Keep your antivirus enabled; if your security software blocks or quarantines it, prefer the built-in Windows options or an alternative tool rather than overriding the protection.
Where this verdict could be wrong2 caveats
- The combined sandbox verdict was clean and the run looked like an ordinary installer placing IObit Unlocker files, so the detections may reflect the product's driver rather than hostile intent.
- Nearly 1,900 distinct sources have submitted the file and it carries a valid signature, which is more typical of distributed commercial software than of a targeted trojan.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- The combined sandbox verdict was clean and the run looked like an ordinary installation
- No injected process was recorded
- Valid code signature and about 1,900 distinct submitters
- Six major antivirus engines detections, including a vulnerable-driver label from ESET
- Sophos and DrWeb label the program a potentially unwanted application
- The signing publisher has almost no history in our records
- The installer registers a shell extension and a persistent program entry
6 sources checked · 5 complete · 1 partial. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 23sandbox rule tags
- 7spawned processes
- 7network contacts
- 40filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Set itself to start automatically after a restart.
Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).
Moderate concern: Ran commands or a script on the test computer.
Moderate concern: Checked whether it was running on a test computer.
Note: Read the user name of the test computer.
Note: Deleted files or logs during the test run (installers often clean up after themselves).
Note: Talked to servers over the internet during the test run.
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.
This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.
Recorded behavior
What happened in the test
Grouped by step. The order is not a timeline.
- 1
Input file
The submitted object
- Evidence 1 of 7: FileSeen in the test run
unlocker-setup (1).exe
25aa598dcc6e5d2eb2e860cf82beb72f38e78d5f562677aa8b0413f64052328f
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
unlocker-setup.exe
"C:\Users\<USER>\Desktop\unlocker-setup.exe"
Test run - Evidence 3 of 7: ProcessSeen in the test run
unlocker-setup.tmp
"C:\Users\<USER>\AppData\Local\Temp\is-MP8BH.tmp\unlocker-setup.tmp" /SL5="$20174,1708085,141824,C:\Users\<USER>\Desktop\unlocker-setup.exe"
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
unlocker-setup.tmp
C:\Users\<USER>\AppData\Local\Temp\is-MP8BH.tmp\unlocker-setup.tmp
Test run - Evidence 5 of 7: Written fileSeen in the test run
_setup64.tmp
C:\Users\<USER>\AppData\Local\Temp\is-B4OTG.tmp\_isetup\_setup64.tmp
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
s1.symcb.com
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
sv.symcb.com
Contacted during the test run.
Test run - +1 more recorded observation
7 facts from the test run. See the full activity list.
What this file did when executed
This file was run in a sandbox and its runtime behaviour was observed.
Sandbox verdicts
1- VT: CLEANclean
Techniques observed in the sandbox
23MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1012
- T1027· Obfuscated code
- T1027.002· Obfuscated code
- T1033· Reads user info
- T1036
- T1045
- T1055· Process injection
- T1059· Runs commands
- T1070· Covers its tracks
- T1071· Application protocol
- T1082· System recon
- T1083· Scans your files
- T1107
- T1112
- T1129· Loads modules
- T1134
- T1485
- T1497· Sandbox evasion
- T1529
- T1548
- T1553
- T1614
- T1614.001
Observed activity
Processes started
7Programs the file ran, with their command lines.
unlocker-setup.exe"C:\Users\<USER>\Desktop\unlocker-setup.exe"unlocker-setup.tmp"C:\Users\<USER>\AppData\Local\Temp\is-MP8BH.tmp\unlocker-setup.tmp" /SL5="$20174,1708085,141824,C:\Users\<USER>\Desktop\unlocker-setup.exe"regsvr32.exe"C:\Windows\system32\regsvr32.exe" /s "C:\Program Files (x86)\IObit\IObit Unlocker\IObitUnlockerExtension.dll"s/s "C:\Program Files (x86)\IObit\IObit Unlocker\IObitUnlockerExtension.dll"IObitUnlocker.exe"C:\Program Files (x86)\IObit\IObit Unlocker\IObitUnlocker.exe"tmpvFBCim.exe
Show all 7 entries for processes started
tmpvFBCim.tmp
Network contacts
77 hosts, listed as 5 domains, 2 addresses, 3 links. Links show the host and path only.
- Domain
s1.symcb.com - Domain
sv.symcb.com - Domain
update.iobit.com - Domain
www.download.windowsupdate.com - Domain
ocsp.digicert.com - IP address
172.66.2.5
Show all 10 entries for network contacts
- IP address
23.53.127.116 - URL
http://s1.symcb.com/pca3-g5.crl - URL
http://sv.symcb.com/sv.crl - URL
http://update.iobit.com/infofiles/iobitunlocker.upt
Files
30Files the file created, changed or deleted.
- Written
C:\Users\<USER>\AppData\Local\Temp\is-MP8BH.tmp\unlocker-setup.tmp - Written
C:\Users\<USER>\AppData\Local\Temp\is-B4OTG.tmp\_isetup\_setup64.tmp - Written
C:\Users\<USER>\AppData\Local\Temp\is-B4OTG.tmp\RdZone.dll - Written
C:\Users\<USER>\AppData\Local\Temp\is-B4OTG.tmp\IObitUnlocker.dll - Written
C:\Users\<USER>\AppData\Local\Temp\is-B4OTG.tmp\Inno_English.lng - Written
C:\Program Files (x86)\IObit\IObit Unlocker\IObitUnlocker.exe
Show all 30 entries for files
- Written
C:\Program Files (x86)\IObit\IObit Unlocker\IObitUnlocker.dll - Written
C:\Program Files (x86)\IObit\IObit Unlocker\IObitUnlockerExtension.dll - Written
C:\Program Files (x86)\IObit\IObit Unlocker\unins000.dat - Written
C:\Program Files (x86)\IObit\IObit Unlocker\is-RRHGU.tmp - Written
C:\Program Files (x86)\IObit\IObit Unlocker\unins000.exe - Written
C:\Program Files (x86)\IObit\IObit Unlocker\is-B9KGA.tmp - Written
C:\Program Files (x86)\IObit\IObit Unlocker\is-E3J4G.tmp - Written
C:\Program Files (x86)\IObit\IObit Unlocker\is-362TO.tmp - Written
C:\Program Files (x86)\IObit\IObit Unlocker\SpecialDir.ini - Deleted
C:\Program Files (x86)\IObit\IObit Unlocker\is-RRHGU.tmp - Deleted
C:\Program Files (x86)\IObit\IObit Unlocker\is-B9KGA.tmp - Deleted
C:\Program Files (x86)\IObit\IObit Unlocker\is-E3J4G.tmp - Deleted
C:\Program Files (x86)\IObit\IObit Unlocker\is-362TO.tmp - Deleted
C:\Program Files (x86)\IObit\IObit Unlocker\is-UIB18.tmp - Deleted
C:\Program Files (x86)\IObit\IObit Unlocker\is-JRPCU.tmp - Deleted
C:\Program Files (x86)\IObit\IObit Unlocker\Language\is-0A6AJ.tmp - Deleted
C:\Program Files (x86)\IObit\IObit Unlocker\Language\is-4P8F5.tmp - Deleted
C:\Program Files (x86)\IObit\IObit Unlocker\Language\is-G02N9.tmp - Deleted
C:\Program Files (x86)\IObit\IObit Unlocker\Language\is-54RM2.tmp - Deleted
C:\Program Files (x86)\IObit\IObit Unlocker\Language\is-G8CV8.tmp - Deleted
C:\Program Files (x86)\IObit\IObit Unlocker\Language\is-6BHPF.tmp - Deleted
C:\Program Files (x86)\IObit\IObit Unlocker\Language\is-C6PPO.tmp - Deleted
C:\Program Files (x86)\IObit\IObit Unlocker\Language\is-VDPDF.tmp - Deleted
C:\Program Files (x86)\IObit\IObit Unlocker\Language\is-R4LB8.tmp
Registry and auto-start
24Settings the file changed, including ways to start again after a restart.
- Auto-start
IObitUnlocker - Set
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CrashControl\CrashDumpEnabled - Set
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CrashControl\MinidumpDir - Set
HKEY_CURRENT_USER\SOFTWARE\Microsoft\RestartManager\Session0000\RegFiles0000 - Set
HKEY_CURRENT_USER\SOFTWARE\Microsoft\RestartManager\Session0000\RegFilesHash - Set
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\IObit Unlocker_is1\Inno Setup: Setup Version
Show all 24 entries for registry and auto-start
- Set
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\IObit Unlocker_is1\Inno Setup: App Path - Set
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\IObit Unlocker_is1\InstallLocation - Set
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\IObit Unlocker_is1\Inno Setup: Icon Group - Set
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\IObit Unlocker_is1\Inno Setup: User - Set
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\IObit Unlocker_is1\Inno Setup: Selected Tasks - Set
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\IObit Unlocker_is1\Inno Setup: Language - Set
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\IObit Unlocker_is1\DisplayName - Set
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\IObit Unlocker_is1\DisplayIcon - Set
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\IObit Unlocker_is1\UninstallString - Set
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\IObit Unlocker_is1\QuietUninstallString - Deleted
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SystemCertificates\AuthRoot\Certificates\28903A635B5280FAE6774C0B6DA7D6BAA64AF2E8 - Deleted
HKEY_CURRENT_USER\SOFTWARE\Microsoft\RestartManager\Session0000\Owner - Deleted
HKEY_CURRENT_USER\SOFTWARE\Microsoft\RestartManager\Session0000\SessionHash - Deleted
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SystemCertificates\AuthRoot\Certificates\4EB6D578499B1CCF5F581EAD56BE3D9B6744A5E5 - Deleted
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SystemCertificates\ROOT\Certificates\BE36A4562FB2EE05DBB3D32323ADF445084ED656 - Deleted
HKEY_CURRENT_USER\SOFTWARE\Microsoft\RestartManager\Session0000\Sequence - Deleted
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Uninstall\IObit Unlocker_is1 - Deleted
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\IObit Unlocker_is1
Mutexes
10Named locks a program uses so only one copy runs; malware families often reuse them.
cversions.3.mmadExceptSettingsMtx$175cHookTThread$175cLocal\RstrMgr-3887CAB8-533F-4C85-B0DC-3E5639F8D511-Session0000Global\C::Users:Virtual:AppData:Local:Microsoft:Windows:Explorer:thumbcache_1024.db!dfMaintainerGlobal\C::Users:Virtual:AppData:Local:Microsoft:Windows:Explorer:thumbcache_idx.db!rwReaderRefs
Show all 10 entries for mutexes
Global\C::Users:Virtual:AppData:Local:Microsoft:Windows:Explorer:thumbcache_idx.db!ThumbnailCacheInitGlobal\C::Users:Virtual:AppData:Local:Microsoft:Windows:Explorer:thumbcache_256.db!dfMaintainerGlobal\C::Users:Virtual:AppData:Local:Microsoft:Windows:Explorer:thumbcache_96.db!dfMaintainerLocal\RstrMgr3887CAB8-533F-4C85-B0DC-3E5639F8D511
Sandbox background — not the file
13The analysis machine's own processes and connections, recorded in every run.
- VM process
Explorer.EXEC:\Windows\Explorer.EXE - VM process
services.exeC:\Windows\system32\services.exe - VM process
svchost.exeC:\Windows\System32\svchost.exe -k NetworkService -p - VM process
svchost.exeC:\Windows\system32\svchost.exe -k UnistackSvcGroup - VM process
svchost.exeC:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted -p -s StorSvc - VM process
lsass.exeC:\Windows\system32\lsass.exe
Show all 13 entries for sandbox background — not the file
- VM process
svchost.exeC:\Windows\system32\svchost.exe -k LocalService -s W32Time - VM process
explorer.exe - VM host
cl-glcb907925.gcdn.co - VM host
assets.msn.com - VM host
224.0.0.252 - VM host
255.255.255.255 - VM host
162.159.36.2
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache. 10 have no saved verdict and were not checked; that is missing coverage, not a finding.
- 01fe66a8aaea0faa04b1…89faaaNot checkedno saved verdict
- ab2752577faa9ff94e1a…86ed3eNot checkedno saved verdict
- 54d53d160f189084b3e5…46998fNot checkedno saved verdict
- eaa9dc1c9dc8620549fe…fb43e7Not checkedno saved verdict
- 01135e3c524fa4cdd5ad…7676d7Not checkedno saved verdict
- ef6b496609073be75cf4…7c10a8Not checkedno saved verdict
- c136b3136d38d13bcc7e…cc2504Not checkedno saved verdict
- 05501e4be5128972bed8…5a6583Not checkedno saved verdict
- 0a9c0405f08aa930a2e8…ca2443Not checkedno saved verdict
- 47d56d71d51c3d4e9643…93abbeNot checkedno saved verdict
Chapter 04
Technical details
16 of the 71 antivirus engines that checked it flag it; signed by ORANGE VIEW LIMITED.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 partial. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 16
- Avast (major engine)Other:Malware-gen [Trj]
- AVG (major engine)Other:Malware-gen [Trj]
- Avira (major engine)TR/W32.Malware
- DrWeb (major engine)Program.Unwanted.5385
- ESET-NOD32 (major engine)Win64/VulnDriver.IObit.A.gen potentially unsafe application
- F-Secure (major engine)Trojan.TR/Malware
- Sophos (major engine)IObit Unlocker (PUA)
- TrellixENS (major engine)Artemis!FF8F2D8CDA29
File fingerprint
- Last analyzed
- Oct 6, 2026, 9:25 PM UTC
- SHA-256
25aa598dcc6e5d2eb2e860cf82beb72f38e78d5f562677aa8b0413f64052328f- SHA-1
89360ff8e2d203eb9fda387cd5398919abac91dd- MD5
ff8f2d8cda2969cb0959338787653b0f
About this file
unlocker-setup (1).exe is a Win32 EXE file of 2.3 MB.
- Type and size
- Win32 EXE · 2.3 MB
- Signer
- ORANGE VIEW LIMITEDValid code signature.
- First seen
- Apr 30, 2026On VirusTotal.
- Submitted by
- 1,906 distinct sources
- Packer
- None detected
- Entropy
- 5.69 of 8
First scanned Updated
Antivirus consensus
16 of 71 engines flagged this file
4 of the 75 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
The 16 detections come from 14 independent scan engines: several vendors license the same engine, so their results are one vote.
- Tier-118 engines6flagged8 vendors sharing 6 engines
- Tier-236 engines4flagged
- Low-trust17 engines4flagged
View all 75 engine results
- AvastMalicious: Other:Malware-gen [Trj]
- AVGMalicious: Other:Malware-gen [Trj]
- AviraMalicious: TR/W32.Malware
- CrowdStrikeMalicious: win/grayware_confidence_60% (D)
- CylanceMalicious: Unsafe
- DeepInstinctMalicious: MALICIOUS
- DrWebMalicious: Program.Unwanted.5385
- ESET-NOD32Malicious: Win64/VulnDriver.IObit.A.gen potentially unsafe application
- F-SecureMalicious: Trojan.TR/Malware
- GoogleMalicious: Detected
- MaxSecureMalicious: Trojan.Malware.682788895.susgen
- PaloaltoMalicious: generic.ml
- RisingMalicious: PUA.VulnDriver!8.1D4E6 (CLOUD)
- SophosMalicious: IObit Unlocker (PUA)
- TrellixENSMalicious: Artemis!FF8F2D8CDA29
- VaristMalicious: W32/ABApplication.WDYC-5249
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- APEXClean
- ArcabitClean
- Avast-MobileNo result
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CTXClean
- CynetClean
- ElasticClean
- EmsisoftClean
- FortinetClean
- GDataClean
- GridinsoftClean
- huorongClean
- IkarusClean
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PandaClean
- SangforClean
- SentinelOneClean
- SkyhighClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrapmineClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
Signatures and behavior heuristics
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
The sandbox recorded persistence through a service or scheduled task. Installers set these up legitimately for their own updaters and services, so this is context, not proof of malicious intent.
EvidenceIObitUnlockerVirusTotal's sandbox summary maps this run to MITRE T1055 (Process Injection), but no injected process of the sample's own was recorded (the analysis VM's own WMI adapter, crash handlers and Chrome updater are not counted). VirusTotal maps T1055 on about half of all files no engine flags, so the mapping alone is not evidence of injection.
EvidenceT1055 (sandbox MITRE mapping)
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.
These identify the compiler, runtime or installer used to build the file. They are not packing and are not a risk signal on their own.
How widely this file has been seen
Widely uploaded, but first seen within the last six months. No strong prior applies.
Chapter 05
Questions & answers
Short answers to the 7 questions people ask most about this file.
Is unlocker-setup (1).exe safe, or is it malware?
What is unlocker-setup (1).exe?
How many antivirus engines detected unlocker-setup (1).exe?
I already downloaded and installed unlocker-setup (1).exe — what should I do?
Is unlocker-setup (1).exe digitally signed?
What is the SHA-256 hash of unlocker-setup (1).exe?
How up to date is this analysis of unlocker-setup (1).exe?
Community
Member reviews and reports for this exact file hash.