Is Zemana.AntiMalware.Setup.exe safe?
Safe file assessment
The hash has a long, established submission history across 2,647 sources.
b548f01428cb26a587…3b3b7bf23fa965Recommended next actions
Before installing
Install it only when it came from the developer's official site or an official app store.
If you already installed 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.
No saved analyst narrative
This report keeps the verified scan facts available below without inventing an analysis that was not saved with the scan.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete5 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial3 of 23 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete7 signature or behavior rules matched.
External intel
Partial1 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
- 23network 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
Zemana.AntiMalware.Setup.exe
b548f01428cb26a5870602e8018adbce814dd2ed53a6b1f74c3b3b7bf23fa965
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\file.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\is-1O9ES.tmp\file.tmp" /SL5="$20196,13025042,780800,C:\Users\<USER>\Desktop\file.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
file.tmp
C:\Users\<USER>\AppData\Local\Temp\is-1O9ES.tmp\file.tmp
04Isolated runtime analysis - Written fileObserved
Setup Log 2024-08-07 #001.txt
C:\Users\<USER>\AppData\Local\Temp\Setup Log 2024-08-07 #001.txt
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
204.79.197.203
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
209.85.200.94
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.
- 204.79.197.203
- 209.85.200.94
- a83f:8110:0:0:1b00:100:2800:0
- a83f:8110:8f:351d:67c6:9a4d:e695:3e9f
- 192.168.0.13
- 192.168.0.4
- a83f:8110:0:0:4e82:21:0:0
- 13.107.4.50
- a83f:8110:0:0:1400:1400:2800:3800
- 209.197.3.8
- http://crt.usertrust.com/USERTrustRSAAddTrustCA.crt
- http://ctldl.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab?04b4644238bd8548
- watson.microsoft.comhttp://watson.microsoft.com/StageOne/Generic/BEX/AntiMalware_exe/3_2_28_0/60633416/clr_dll/4_0_30319_17929/4ffa5753/0023e359/c0000409/00000000.htm?LCID=1033&OS=6.1.7601.2.00010100.1.0.48.17514&SM=LENOVO&SPN=2241W2U&BV=7UET92WW%20(3.22%20)&MID=F2EC8DC6-EB4A-4B44-95EF-9B81DC7C287B
- amsdk
- C:\Users\<USER>\AppData\Local\Temp\is-1O9ES.tmp\file.tmp
- C:\Users\<USER>\AppData\Local\Temp\Setup Log 2024-08-07 #001.txt
- C:\Users\<USER>\AppData\Local\Temp\is-RRSJP.tmp\_isetup\_setup64.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-RRSJP.tmp\AMSDKCore399001.dll
- C:\Users\<USER>\AppData\Local\Temp\is-RRSJP.tmp\Partners.ini
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERC11.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERCBC.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERCEC.tmp.txt
- C:\Windows\System32\spp\store\2.0\cache\cache.dat
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER298B.tmp.WERInternalMetadata.xml
- Local\MSCTF.Asm.MutexDefault1
- madExceptSettingsMtx$494
- Global\e4e6189c920c633c7d586a7b8351c7dc.trace
- DefaultTabtip-MainUI
- Global\C::Users:user:AppData:Local:Microsoft:Windows:Explorer:thumbcache_idx.db!rwWriterMutex
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- c0c7e61f5d7f57f14f67…736590Never scannednever seen before
- b6a8596d7d5a2a2b4a8a…cd29deNever scannednever seen before
- 388a796580234efc95f3…136f95Never scannednever seen before
- 9942fff044a14df4a876…a94220Never scannednever seen before
- ca10cd00b06593f4ce25…4cf269Never scannednever seen before
- 2c63c9035a5794423fcf…7d3bb5Never scannednever seen before
- bd5acd4d27639792d36a…af48afNever scannednever seen before
- 2b0ee097f75a7af15519…5ec4f8Never scannednever seen before
- bfef2e8e71c72061bd0f…b8c04aNever scannednever seen before
- f7d43b82eaffa7efbf66…6f6ed6Never 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.
- 7rule hits recorded
- 5 / 75engines flagged
- 2,647sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
The hash has a long, established submission history across 2,647 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 02
One or more independent reference checks were incomplete or unavailable.
ProvenanceDerivedSourceExternal-intelligence coverageObserved at - 03
The file has a valid code signature from Zemana D.O.O. Sarajevo.
ProvenanceObservedSourceCode-signing metadataObserved at - 04
Scanned file: Zemana.AntiMalware.Setup.exe — b548f01428cb26a5870602e8018adbce814dd2ed53a6b1f74c3b3b7bf23fa965
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\file.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\<USER>\AppData\Local\Temp\is-1O9ES.tmp\file.tmp" /SL5="$20196,13025042,780800,C:\Users\<USER>\Desktop\file.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: file.tmp — C:\Users\<USER>\AppData\Local\Temp\is-1O9ES.tmp\file.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: Setup Log 2024-08-07 #001.txt — C:\Users\<USER>\AppData\Local\Temp\Setup Log 2024-08-07 #001.txt
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 204.79.197.203 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 209.85.200.94 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
One or more independent reference databases matched 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.
- PE_Digital_Certificate
- PE_Potentially_Signed_Digital_Certificate
- shellcode
- Suspicious_Macro_Presence
Sandbox flagged persistence indicators (registry Run keys / services / scheduled tasks).
EvidenceamsdkMITRE 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>\Desktop\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.
Evidence204.79.197.203 · 209.85.200.94 · a83f:8110:0:0:1b00:100:2800:0
5 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
- Zemana.AntiMalware.Setup.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: Zemana D.O.O. Sarajevo
- Size
- 13.3 MB
- Last analyzed
- May 2, 2026, 10:49 AM UTC
b548f01428cb26a5870602e8018adbce814dd2ed53a6b1f74c3b3b7bf23fa965Safety & 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
Install it only when it came from the developer's official site or an official app store.
- 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 Zemana.AntiMalware.Setup.exe safe?
What is Zemana.AntiMalware.Setup.exe?
How many antivirus engines detected Zemana.AntiMalware.Setup.exe?
Is Zemana.AntiMalware.Setup.exe digitally signed?
What is the SHA-256 hash of Zemana.AntiMalware.Setup.exe?
Is it safe to install Zemana.AntiMalware.Setup.exe?
How up to date is this analysis of Zemana.AntiMalware.Setup.exe?
Community
Member reviews and reports for this exact file hash.
