File scan report
Verdict Suspicious
Is Setup.
One less reliable engine flags Trojan.Zenpak while 16 major antivirus engines report clean.
Why Suspicious? One antivirus engine (Jiangmin) flags it; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
Treat as suspicious pending further sandbox or manual analysis; avoid execution until additional confirmation is obtained.
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
1 of 70 flagged
- Flagged 1
- No detection 69
- No result 5
- Code signing Signer not verified
- Test run Completed
- First seen 3y ago
Chapter 02
Why we think so
2 points against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Prevalence is widely seen and long established but behaviour raises red flags on an otherwise quiet sample.
The file is a 4 MB signed EXE submitted on Sep 7, 2023 with widely seen and long established prevalence. Engines show only a single less reliable detection and no major consensus. No complete contacted-host reputation result was available, and no external intel hits. The combination of clean engine majority and suspicious activity in the test run places the file in mixed-signals territory.
What We Detected
71 engines scanned the sample; only Jiangmin returned a malicious label (Trojan.Zenpak.oyd). All 16 major antivirus engines reported clean. The binary is signed by Kaspersky Lab JSC but carries no established signer history in our records. Sandbox execution revealed MITRE T1055 (process injection) and T1562.001 (impair defenses) plus access to the Windows password store and 18 direct-IP connections with zero DNS lookups.
Threat Behavior
Multiple dropped files and temporary directories were created during execution, consistent with an installer or downloader. No malicious files it created or known-bad hosts were observed.
What To Do Now
Do not execute on production systems. Submit the sample to additional sandboxes or threat-intel platforms for deeper behavioural analysis. Monitor for similar hashes or the listed contacted IPs.
Where this verdict could be wrong1 caveat
- Community comment lists unrelated families (#amadey etc.) with no engine or YARA corroboration — likely noise rather than confirmation.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 16 major antivirus engines reported clean
- Common_old prevalence across 191 sources
- No malicious files it created or cached malicious hosts
- Direct-IP a control server with no DNS resolution
- Less reliable engine detection of Zenpak family
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- 29sandbox rule tags
- 8spawned processes
- 12network contacts
- 38filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).
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: Listed the programs running on 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 creating a scheduled task; none was recorded.
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.
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
Setup.exe
b789785c7fc746504b2ffa45c6f5ede63ad199eed400624b7faf8ff27e8cb271
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
file.exe
"C:\Users\<USER>\Desktop\file.exe"
Test run - Evidence 3 of 7: ProcessSeen in the test run
file.exe
"C:\Windows\temp\B65C0567CEE90F11B95743796FD35D5C\file.exe" -initialNonSecureSetupPath="C:\Users\<USER>\Desktop\file.exe"
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
Temp
C:\Users\<USER>\AppData\Local\Temp
Test run - Evidence 5 of 7: Written fileSeen in the test run
Kaspersky Lab Setup Files
C:\ProgramData\Kaspersky Lab Setup Files
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
62.67.238.152
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
4.28.136.57
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.
Techniques observed in the sandbox
29MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1010
- T1012
- T1018
- T1027· Obfuscated code
- T1027.002· Obfuscated code
- T1027.005· Obfuscated code
- T1036
- T1053· Scheduled task
- T1055· Process injection
- T1057· Lists programs
- T1070· Covers its tracks
- T1070.006· Covers its tracks
- T1071· Application protocol
- T1082· System recon
- T1083· Scans your files
- T1095· Custom network
- T1105· Network file transfer
- T1106
- T1112
- T1129· Loads modules
- T1202
- T1497· Sandbox evasion
- T1518· Checks your AV
- T1518.001· Checks your AV
- T1539
- T1553
- T1562· Disables security
- T1562.001· Disables security
- T1573
Observed activity
Processes started
8Programs the file ran, with their command lines.
file.exe"C:\Users\<USER>\Desktop\file.exe"file.exe"C:\Windows\temp\B65C0567CEE90F11B95743796FD35D5C\file.exe" -initialNonSecureSetupPath="C:\Users\<USER>\Desktop\file.exe"startup.exe"C:\ProgramData\Kaspersky Lab Setup Files\KFA21.22.7.466.0.384.0\au_setup_846F305C-9EEC-11F0-9B75-3497F63DD5C5\startup.exe" -initialNonSecureSetupPath="C:\Users\<USER>\Desktop\file.exe" -auto_update_mode="C:\Users\<USER>\Desktop\file.exe" /-self_remove -l=en -xpos=330 -ypos=223 -prevsetupver=21.14.5.462.0.190.0startup.exe"C:\Windows\temp\C7988858CEE90F11B95743796FD35D5C\startup.exe" -initialNonSecureSetupPath="C:\Users\<USER>\Desktop\file.exe" -auto_update_mode="C:\Users\<USER>\Desktop\file.exe" /-self_remove -l=en -xpos=330 -ypos=223 -prevsetupver=21.14.5.462.0.190.0setup_ui.exe"C:\Users\<USER>\AppData\Local\Temp\2CD12068CEE90F11B95743796FD35D5C\setup_ui.exe" -cp=objref:TUVPVwEAAAAAAAAAAAAAAMAAAAAAAABGgQIAAAAAAAAhJ2hCxgaiKeQoq9k1IMbNAuAAACga//8P9IamDQv0azQAHgAHAEQARQBTAEsAVABPAFAALQBFAFQANQAxAEEASgBPAAAABwAxADcAMgAuADEANgAuADEALgA0AAAAAAAJAP//AAAeAP//AAAQAP//AAAKAP//AAAWAP//AAAfAP//AAAOAP//AAAAAA==:file.exe"C:\Windows\temp\B65C0567CEE90F11B95743796FD35D5C\file.exe" -cleanup="C:\Users\<USER>\AppData\Local\Temp\CAB6A377CEE90F11B95743796FD35D5C;5856"
Show all 8 entries for processes started
startup.exe%SAMPLEPATH%\startup.exestartup.exeC:\Windows\Temp\7BC736E379D4EE11E81C0051D500724E\startup.exe
Network contacts
1212 hosts, listed as 11 addresses, 1 link. Links show the host and path only.
- IP address
62.67.238.152 - IP address
4.28.136.57 - IP address
82.202.185.146 - IP address
66.110.49.8 - IP address
4.31.156.204 - IP address
82.202.185.148
Show all 12 entries for network contacts
- IP address
104.18.21.226 - IP address
81.19.104.172 - IP address
151.101.22.133 - IP address
23.219.78.81 - IP address
23.96.180.189 - URL
http://crl.kaspersky.com/aia/KasperskyLabPublicServicesRootCertificationAuthority.crt
Files
30Files the file created, changed or deleted.
- Written
C:\Users\<USER>\AppData\Local\Temp - Written
C:\ProgramData\Kaspersky Lab Setup Files - Written
C:\Windows\Temp\B65C0567CEE90F11B95743796FD35D5C\file.exe - Written
C:\Users\<USER>\AppData\Local\Temp\CAB6A377CEE90F11B95743796FD35D5C\setup.dll - Written
C:\Users\<USER>\AppData\Local\Temp\kl-setup-2025-10-01-14-11-31_KAV.21.14.5.462.log - Written
C:\Users\<USER>\AppData\Local\Temp\773A6BAD-9EEC-11F0-9B75-3497F63DD5C5\downloader_neutral.ini
Show all 30 entries for files
- Written
C:\Users\<USER>\AppData\Local\Temp\773A6BAD-9EEC-11F0-9B75-3497F63DD5C5\GuiStrings.loc - Written
C:\Users\<USER>\AppData\Local\Temp\773A6BAD-9EEC-11F0-9B75-3497F63DD5C5\downloader_neutral_KFA.ini - Written
C:\Users\<USER>\AppData\Local\Temp\773A6BAD-9EEC-11F0-9B75-3497F63DD5C5\GuiStrings_KFA.loc - Written
C:\Users\<USER>\AppData\Local\Temp\773A6BAD-9EEC-11F0-9B75-3497F63DD5C5\html\install_programm.png - Written
C:\Users\<USER>\AppData\Local\Temp\773A6BAD-9EEC-11F0-9B75-3497F63DD5C5\html\product.png - Written
C:\Users\<USER>\AppData\Local\Temp\773A6BAD-9EEC-11F0-9B75-3497F63DD5C5\html\product.svg - Written
C:\Users\<USER>\AppData\Local\Temp\kl-setup-2025-10-01-14-11-34_KFA.21.14.5.462.log - Written
C:\Users\<USER>\AppData\Local\Temp\CAB6A377CEE90F11B95743796FD35D5C\kasperskylab.setup.ui.visuals.dll - Written
C:\Users\<USER>\AppData\Local\Temp\CAB6A377CEE90F11B95743796FD35D5C\kasperskylab.setup.ui.core.dll - Deleted
C:\Users\<USER>\AppData\Local\Temp\kl-setup-2025-10-01-14-11-31_KAV.21.14.5.462.log - Deleted
C:\ProgramData\Kaspersky Lab Setup Files\KFA21.22.7.466.0.384.0\au_setup_846F305C-9EEC-11F0-9B75-3497F63DD5C5 - Deleted
C:\ProgramData\Kaspersky Lab Setup Files\KFA21.22.7.466.0.384.0 - Deleted
C:\Windows\Temp\B65C0567CEE90F11B95743796FD35D5C\file.exe - Deleted
C:\Windows\Temp\B65C0567CEE90F11B95743796FD35D5C - Deleted
C:\ProgramData\Kaspersky Lab Setup Files - Deleted
C:\Users\<USER>\AppData\Local\Temp\773A6BAD-9EEC-11F0-9B75-3497F63DD5C5\downloader_en.ini - Deleted
C:\Users\<USER>\AppData\Local\Temp\773A6BAD-9EEC-11F0-9B75-3497F63DD5C5\downloader_en_KFA.ini - Deleted
C:\Users\<USER>\AppData\Local\Temp\773A6BAD-9EEC-11F0-9B75-3497F63DD5C5\downloader_neutral.ini - Deleted
C:\Users\<USER>\AppData\Local\Temp\773A6BAD-9EEC-11F0-9B75-3497F63DD5C5\downloader_neutral_KFA.ini - Deleted
C:\Users\<USER>\AppData\Local\Temp\773A6BAD-9EEC-11F0-9B75-3497F63DD5C5\eula_en.txt - Deleted
C:\Users\<USER>\AppData\Local\Temp\773A6BAD-9EEC-11F0-9B75-3497F63DD5C5\eula_gdpr_en.txt - Deleted
C:\Users\<USER>\AppData\Local\Temp\773A6BAD-9EEC-11F0-9B75-3497F63DD5C5\GuiStrings.loc - Deleted
C:\Users\<USER>\AppData\Local\Temp\773A6BAD-9EEC-11F0-9B75-3497F63DD5C5\GuiStrings_en.loc - Deleted
C:\Users\<USER>\AppData\Local\Temp\773A6BAD-9EEC-11F0-9B75-3497F63DD5C5\GuiStrings_en_KFA.loc
Registry and auto-start
1Settings the file changed, including ways to start again after a restart.
- Deleted
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SystemCertificates\AuthRoot\Certificates\D69B561148F01C77C54578C10926DF5B856976AD
Mutexes
8Named locks a program uses so only one copy runs; malware families often reuse them.
Kaspersky_Setup_Single_InstanceDBWinMutex\Sessions\1\BaseNamedObjects\Kaspersky_Setup_Single_Instance\Sessions\1\BaseNamedObjects\Local\ZonesCacheCounterMutex\Sessions\1\BaseNamedObjects\Local\ZonesLockedCacheCounterMutex\Sessions\1\BaseNamedObjects\DBWinMutex
Show all 8 entries for mutexes
\Sessions\1\BaseNamedObjects\Local\__DDrawExclMode__\Sessions\1\BaseNamedObjects\Local\__DDrawCheckExclMode__
Sandbox background — not the file
16The analysis machine's own processes and connections, recorded in every run.
- 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 - VM process
svchost.exeC:\Windows\system32\svchost.exe -k LocalService -s W32Time
Show all 16 entries for sandbox background — not the file
- VM process
wuapihost.exeC:\Windows\System32\wuapihost.exe - VM host
192.229.211.108 - VM host
20.99.133.109 - VM host
23.198.171.50 - VM host
20.99.185.48 - VM host
192.168.0.50 - VM host
52.154.209.174 - VM host
23.216.81.152 - VM host
20.99.186.246 - VM host
192.168.0.15
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.
- 729106b3b2e792d3015b…00ed73Not checkedno saved verdict
- 1dd62c569fd35e3f383a…a60d87Not checkedno saved verdict
- 6e1f18b7db3ef6cbec96…ef6466Not checkedno saved verdict
- cbb72cdc1e461226c7d0…8edc78Not checkedno saved verdict
- 592ae0dfc01dc6afb25f…0612f1Not checkedno saved verdict
- 41c6a3c5eb79e1b74e7e…4ccd2aNot checkedno saved verdict
- ec8f4977dce0076aa4a7…173572Not checkedno saved verdict
- 4a2260f0d29925bbcf11…c759fcNot checkedno saved verdict
- 88de26ddc2d370bcf16a…319c8eNot checkedno saved verdict
- b1f443629bab7b8dc801…852c02Not checkedno saved verdict
Chapter 04
Technical details
1 of the 70 antivirus engines that checked it flags it; a signature that did not verify.
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 1
- JiangminTrojan.Zenpak.oyd
File fingerprint
- Last analyzed
- Jul 12, 2026, 10:11 AM UTC
- SHA-256
b789785c7fc746504b2ffa45c6f5ede63ad199eed400624b7faf8ff27e8cb271- SHA-1
5f1e8f3e21da7da41f14ac12d6496418cd7af657- MD5
f9a81f54651883068ddb6c9502a83869
About this file
Setup.exe is a Win32 EXE file of 4.4 MB.
- Type and size
- Win32 EXE · 4.4 MB
- Signer
- Kaspersky Lab JSC (unverified signature)Worth noting: Malware sometimes copies or steals a company's signature, so this does not mean that company made it.
- First seen
- Sep 7, 2023On VirusTotal.
- Submitted by
- 191 distinct sources
- Packer
- None detected
- Entropy
- 7.25 of 8
First scanned Updated
Antivirus consensus
1 of 70 engines flagged this file
5 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.
- Tier-117 engines0flagged
- Tier-236 engines0flagged
- Low-trust17 engines1flagged
View all 75 engine results
- JiangminMalicious: Trojan.Zenpak.oyd
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- APEXClean
- ArcabitClean
- AvastClean
- Avast-MobileNo result
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceClean
- CynetClean
- DeepInstinctClean
- DrWebClean
- ElasticClean
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleClean
- GridinsoftClean
- huorongClean
- IkarusNo result
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoClean
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrapmineClean
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
VirusTotal'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.
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.
Chapter 05
Questions & answers
Short answers to the 7 questions people ask most about this file.
Is Setup.exe safe, or is it malware?
What is Setup.exe?
How many antivirus engines detected Setup.exe?
I already downloaded and installed Setup.exe — what should I do?
Is Setup.exe digitally signed?
What is the SHA-256 hash of Setup.exe?
How up to date is this analysis of Setup.exe?
Community
Member reviews and reports for this exact file hash.