Is simpleunlocker_release (1).zip safe?
ZIP archive containing MSIL binaries that exhibit process injection and contact external IPs, flagged by three tier-1 engines.
Three tier-1 engines detect malicious behavior and the sandbox shows process injection plus direct-IP traffic. No strong family consensus exists and dropped children returned clean, leaving mixed signals.
9768bf823d8f801913…7c9f225651d78fRecommended next actions
Before opening or extracting
Do not open or extract it until the source can be verified independently.
If you already opened or extracted it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the original trusted source and verify its exact hash when possible.
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.
Three tier-1 engines detect malicious behavior and the sandbox shows process injection plus direct-IP traffic. No strong family consensus exists and dropped children returned clean, leaving mixed signals.
The file is a ZIP that extracts multiple PE components. Runtime evidence maps to T1055 and T1562.001, and three tier-1 engines label the sample malicious. However, the tier-1 family consensus is weak, 14 tier-1 engines cleared it, and no dropped child or cached host is confirmed malicious. Community notes reference several infostealer families, but prevalence is common_old. These conflicting indicators place the sample in the suspicious band.
What We Detected
10 of 74 engines flagged the archive. Fortinet, Ikarus and TrendMicro (tier-1) 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 tier-1 consensus here.
What To Do Now
Do not execute the archive. Keep endpoint protection 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 wrong3 caveats
- tier1FamilyConsensus.strong=false (only 1 tier-1 engine on 'behavior' label) and 14 tier-1 engines reported clean.
- droppedChildren.hasMaliciousChild=false and contactedHosts.maliciousHosts.length=0 — no confirmed malicious child or cached host hit.
- prevalence is common_old rather than rare_new, which can indicate a long-lived PUA 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.
- 14 tier-1 engines reported clean
- No malicious child files detected
- No cached malicious hosts contacted
- Process injection capability (T1055)
- Defense evasion observed (T1562.001)
- Direct-IP network traffic without domain
- Multiple infostealer family references in community notes
Treat as untrusted; delete the archive and do not run any extracted executables until a definitive clean verdict is obtained from multiple high-trust scanners.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete10 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 of 3 contacted hosts were cross-checked; coverage is incomplete.
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
- 15MITRE ATT&CK techniques
- 15spawned processes
- 3network contacts
- 16filesystem & 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: Attempted to impair or bypass security controls.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Removed execution artefacts or logs, which can conceal activity.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Communicates over the network in a non-standard way.
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
simpleunlocker_release (1).zip
9768bf823d8f801913705dca9032b83b6912061c3a7b4bb7f47c9f225651d78f
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\simpleunlocker_release/bin/AntiGDI.dll",#1
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\simpleunlocker_release/bin/AntiGDI_Injector.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
EasyHook32Svc.exe.log
C:\Users\<USER>\AppData\Local\Microsoft\CLR_v4.0_32\UsageLogs\EasyHook32Svc.exe.log
04Isolated runtime analysis - Written fileObserved
EasyHook64Svc.exe.log
C:\Users\<USER>\AppData\Local\Microsoft\CLR_v4.0\UsageLogs\EasyHook64Svc.exe.log
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
104.21.1.131
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
172.67.129.68
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.
- 104.21.1.131
- 172.67.129.68
- http://simpleunlocker.ds1nc.ru/release/version.xml
- C:\Users\<USER>\AppData\Local\Microsoft\CLR_v4.0_32\UsageLogs\EasyHook32Svc.exe.log
- C:\Users\<USER>\AppData\Local\Microsoft\CLR_v4.0\UsageLogs\EasyHook64Svc.exe.log
- C:\Users\<USER>\AppData\Local\Microsoft\CLR_v4.0_32\UsageLogs\rundll32.exe.log
- C:\Users\<USER>\AppData\Local\Microsoft\CLR_v4.0\UsageLogs\rundll32.exe.log
- C:\Users\<USER>\AppData\Local\Microsoft\CLR_v4.0_32\UsageLogs\su_updater.exe.log
- Global\netfxeventlog.1.0
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 76ae3da1149711aabeda…16c684Never scannednever seen before
- 10a10aac162dc08c85a0…2d7b34Never scannednever seen before
- ad26b4df8a73ebdbc526…f55e68Never scannednever seen before
- 8267ea2acb222dad1501…d47256Never scannednever seen before
- 960c791d60da56641cea…64c52dNever scannednever seen before
- 1469b54d8c0b8abf370c…180fdaNever scannednever seen before
- 39361867b97155b16fe6…72c8dbNever scannednever seen before
- 96c54111b24ca7936a88…a7d20eNever scannednever seen before
- db1e5b4acd912fd1d999…27afb5Never scannednever seen before
- 644b699e988e3fbe6e02…325529Never 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
- 10 / 74engines flagged
- 3,098sources 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
10 of 74 antivirus engines flagged the file, including Fortinet and Google.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has a long, established submission history across 3,098 sources.
ProvenanceDerivedSourceSubmission historyObserved at - 04
Scanned file: simpleunlocker_release (1).zip — 9768bf823d8f801913705dca9032b83b6912061c3a7b4bb7f47c9f225651d78f
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\simpleunlocker_release/bin/AntiGDI.dll",#1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\<USER>\AppData\Local\Temp\simpleunlocker_release/bin/AntiGDI_Injector.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: EasyHook32Svc.exe.log — C:\Users\<USER>\AppData\Local\Microsoft\CLR_v4.0_32\UsageLogs\EasyHook32Svc.exe.log
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: EasyHook64Svc.exe.log — C:\Users\<USER>\AppData\Local\Microsoft\CLR_v4.0\UsageLogs\EasyHook64Svc.exe.log
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 104.21.1.131 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 172.67.129.68 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: infostealer
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.
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.
Evidence"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\simpleunlocker_release/bin/AntiGDI.dll",#1The 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.
Evidence104.21.1.131 · 172.67.129.68
10 of 74 engines flagged this file
View all 74 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
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
- simpleunlocker_release (1).zip
- Format
- ZIP
- Code signing
- Not applicable to this file type
- Size
- 944.0 KB
- Last analyzed
- Jul 25, 2026, 4:15 PM UTC
9768bf823d8f801913705dca9032b83b6912061c3a7b4bb7f47c9f225651d78fSafety & 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 open or extract 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 archive and use a fresh copy from a trusted source. Get a fresh copy from the original trusted source and verify its exact hash when possible.
- 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 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?
How do I remove simpleunlocker_release (1).zip?
What kind of malware is simpleunlocker_release (1).zip?
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.