File scan report
Verdict Suspicious
Is simpleunlocker_ release (1). zip safe? Treat it as suspicious.
No strong family consensus exists and files it created returned clean, leaving mixed signals.
Why Suspicious? 10 antivirus engines flag it; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
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 open or extract 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 opened or extracted 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
10 of 66 flagged
- Flagged 10
- No detection 56
- No result 8
- Code signing Not applicable
- Test run Completed
- First seen 1y ago
Chapter 02
Why we think so
3 points against it and 2 in its favour, checked against the scan evidence.
The reasoning behind this verdict
The file is a ZIP that extracts multiple PE components. Evidence from the test run maps to and T1562.001, and three major antivirus engines label the sample malicious. However, the major family consensus is weak, 14 major antivirus engines cleared it, and no file it created or cached host is confirmed malicious. Community notes reference several infostealer families, but prevalence is widely seen and long established. These conflicting indicators place the sample in the suspicious band.
What We Detected
10 of the 66 antivirus engines that checked it flagged the archive. Fortinet, Ikarus and TrendMicro (major) reported malicious behavior or MSIL trojan labels. Sandbox execution revealed rundll32 loading AntiGDI.dll and EasyHook libraries, consistent with process injection (T1055) and defense evasion (T1562.001). Two direct-IP addresses were contacted and several .NET executables were dropped to the user temp folder.
Threat Behavior
The extracted binaries appear to implement hooking and injection routines typical of credential-stealing or remote-access tooling. Community researchers have linked the hash to Azorult, LokiBot and Chimera families in external reports, although no single family achieved major consensus here.
What To Do Now
Do not execute the archive. Keep security software enabled. If the file was downloaded from an untrusted source, delete it and scan the system with a full antivirus sweep. Avoid re-downloading similar 'unlocker' utilities from unofficial sites.
Where this verdict could be wrong2 caveats
- droppedChildren.hasMaliciousChild=false and contactedHosts.maliciousHosts.length=0 — no confirmed malicious child or cached host hit.
- prevalence is widely seen and long established rather than rare and which can indicate a long-lived unwanted program or cracked utility rather than fresh malware campaign.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- No malicious files it created detected
- No cached malicious hosts contacted
- Defense evasion observed
- Direct-IP network traffic without domain
- Multiple infostealer family references in community notes
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- 15sandbox rule tags
- 14spawned processes
- 3network contacts
- 16filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Ran commands or a script on the test computer.
Moderate concern: Used an unusual way to talk to a server.
Moderate concern: Downloaded a file during the test run.
Moderate concern: Checked whether it was running on a 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.
Note: Read basic details of the test computer, such as its Windows version.
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.
Not confirmed: A sandbox rule tagged this run as weakening security settings; no setting change was recorded.
Not confirmed: A sandbox rule tagged this run as changing how Windows loads code; nothing confirms it.
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
simpleunlocker_release (1).zip
9768bf823d8f801913705dca9032b83b6912061c3a7b4bb7f47c9f225651d78f
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
rundll32.exe
"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\simpleunlocker_release/bin/AntiGDI.dll",#1
Test run - Evidence 3 of 7: ProcessSeen in the test run
AntiGDI_Injector.exe
"C:\Users\<USER>\AppData\Local\Temp\simpleunlocker_release/bin/AntiGDI_Injector.exe"
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
EasyHook32Svc.exe.log
C:\Users\<USER>\AppData\Local\Microsoft\CLR_v4.0_32\UsageLogs\EasyHook32Svc.exe.log
Test run - Evidence 5 of 7: Written fileSeen in the test run
EasyHook64Svc.exe.log
C:\Users\<USER>\AppData\Local\Microsoft\CLR_v4.0\UsageLogs\EasyHook64Svc.exe.log
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
104.21.1.131
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
172.67.129.68
Contacted during the test run.
Test run - +1 more recorded observation
7 facts from the test run. See the full activity list.
Includes 15 mapped techniques, every process, file, registry and network entry and 10 dropped files.
Show the technical evidenceChapter 04
Technical details
10 of the 66 antivirus engines that checked it flag it.
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 10
- Fortinet (major engine)Malicious_Behavior.SB
- Ikarus (major engine)Trojan.MSIL.Krypt
- TrellixENS (major engine)Artemis!4273A495E9CA
- TrendMicro (major engine)Trojan.MSIL.DISTOOL.TL0101ER26ZS
- GoogleDetected
- GridinsoftSpy.U.AzorUlt.tr
- MaxSecureTrojan.Malware.300983.susgen
- RisingTrojan.Distool!8.1B9E3 (CLOUD)
File fingerprint
- Last analyzed
- Jul 25, 2026, 4:15 PM UTC
- SHA-256
9768bf823d8f801913705dca9032b83b6912061c3a7b4bb7f47c9f225651d78f- SHA-1
682bbf531b12d036d6a9133792b5df5b9b1073b7- MD5
53983ab653bbef58fcbe634f67d04850
About this file
simpleunlocker_release (1).zip is a ZIP file of 966.6 kB.
- Type and size
- ZIP · 966.6 kB
- Signer
- Not applicable
- First seen
- Jun 3, 2025On VirusTotal.
- Submitted by
- 3,098 distinct sources
First scanned
Includes every engine result (74), 1 matched signature rule and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is simpleunlocker_release (1).zip safe, or is it malware?
What is simpleunlocker_release (1).zip?
How many antivirus engines detected simpleunlocker_release (1).zip?
I already downloaded and opened or extracted simpleunlocker_release (1).zip — what should I do?
What is the SHA-256 hash of simpleunlocker_release (1).zip?
How up to date is this analysis of simpleunlocker_release (1).zip?
Community
Member reviews and reports for this exact file hash.