Suspicious
Signed installer with process-injection and LSASS activity flagged by sandbox heuristics despite near-zero engine detections.
b789785c7fc746504b…f27e8cb271The verdict, reasoned out.
Not a rules engine. The MT AI Engine reads every signal we collected, weighs them against history, and commits to an answer.
The file is a 4 MB signed EXE submitted over 1000 days ago with common_old prevalence. Engines show only a single low-trust detection and no tier-1 consensus. However, sandbox behaviour includes high-severity process injection, credential-dumping style LSASS access, and direct-IP C2 without DNS — all classic malware indicators. No malicious children, no malicious hosts in cache, and no external intel hits. The combination of clean engine majority and suspicious runtime activity places the file in mixed-signals territory.
Each signal cites a concrete token from the evidence the arbiter saw — engine name, MITRE technique, signer string, or an exact count.
engines: 1/71 malicious (Jiangmin low_trust), tier1Malicious=0, onlyLowTrustFlagging=true
signing.signer='Kaspersky Lab JSC' with no signerStats history
behaviour.offensiveTechniques=['T1055','T1562.001'] and three triggeredHeuristics (ProcessInjection high, CredentialDumper medium, DirectIpC2 medium)
prevalence.classification=common_old (191 sources), droppedChildren.hasMaliciousChild=false
- 16 tier-1 engines reported clean
- Common_old prevalence across 191 sources
- No malicious dropped children or cached malicious hosts
- Sandbox observed process injection (T1055) and LSASS access
- Direct-IP C2 with no DNS resolution
- Low-trust engine detection of Zenpak family
Treat as suspicious pending further sandbox or manual analysis; avoid execution until additional confirmation is obtained.
zenpak corroborated by 2 sources
- VT (75 engines)zenpak
- MT AI Enginezenpak
1 contradiction resolved by the scoring engine
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.
- 62.67.238.152
- 4.28.136.57
- 82.202.185.146
- 66.110.49.8
- 4.31.156.204
- 192.229.211.108
- 20.99.133.109
- 82.202.185.148
- 23.198.171.50
- 104.18.21.226
- http://crl.kaspersky.com/aia/KasperskyLabPublicServicesRootCertificationAuthority.crt
- C:\Users\<USER>\AppData\Local\Temp
- C:\ProgramData\Kaspersky Lab Setup Files
- C:\Windows\Temp\B65C0567CEE90F11B95743796FD35D5C\file.exe
- C:\Users\<USER>\AppData\Local\Temp\CAB6A377CEE90F11B95743796FD35D5C\setup.dll
- C:\Users\<USER>\AppData\Local\Temp\kl-setup-2025-10-01-14-11-31_KAV.21.14.5.462.log
- C:\Users\<USER>\AppData\Local\Temp\kl-setup-2025-10-01-14-11-31_KAV.21.14.5.462.log
- C:\ProgramData\Kaspersky Lab Setup Files\KFA21.22.7.466.0.384.0\au_setup_846F305C-9EEC-11F0-9B75-3497F63DD5C5
- C:\ProgramData\Kaspersky Lab Setup Files\KFA21.22.7.466.0.384.0
- C:\Windows\Temp\B65C0567CEE90F11B95743796FD35D5C\file.exe
- C:\Windows\Temp\B65C0567CEE90F11B95743796FD35D5C
- Kaspersky_Setup_Single_Instance
- DBWinMutex
- \Sessions\1\BaseNamedObjects\Kaspersky_Setup_Single_Instance
- \Sessions\1\BaseNamedObjects\Local\ZonesCacheCounterMutex
- \Sessions\1\BaseNamedObjects\Local\ZonesLockedCacheCounterMutex
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 729106b3b2e792d3015b…00ed73Never scannednever seen before
- 1dd62c569fd35e3f383a…a60d87Never scannednever seen before
- 6e1f18b7db3ef6cbec96…ef6466Never scannednever seen before
- cbb72cdc1e461226c7d0…8edc78Never scannednever seen before
- 592ae0dfc01dc6afb25f…0612f1Never scannednever seen before
- 41c6a3c5eb79e1b74e7e…4ccd2aNever scannednever seen before
- ec8f4977dce0076aa4a7…173572Never scannednever seen before
- 4a2260f0d29925bbcf11…c759fcNever scannednever seen before
- 88de26ddc2d370bcf16a…319c8eNever scannednever seen before
- b1f443629bab7b8dc801…852c02Never scannednever seen before
YARA + heuristic rules that fired
A researcher-curated or high-severity heuristic rule matched this sample. These rules target specific malware families and are near-definitive.
MITRE T1055 (Process Injection) observed — CreateRemoteThread / APC / reflective-DLL injection. The payload is being smuggled into a legitimate process to bypass AV hooks.
EvidenceC:\Windows\System32\svchost.exe -k NetworkService -pSandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.
EvidenceC:\Windows\system32\lsass.exeSample contacted 18 external IP address(es) and zero domains. Benign software virtually always uses DNS; no-DNS direct-IP C2 is a strong malware indicator because it bypasses reputation systems and dodges domain-based blocklists.
Evidence62.67.238.152 · 4.28.136.57 · 82.202.185.146
1 detection across 75 engines
Section entropy & packers
Section-level entropy and packer detection from the PE header. Nothing suspicious here — entropy is within the normal range for unpacked code.
How often this file shows up in the wild
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Forensic fingerprint
- File name
- Setup.exe
- Size
- 4.17 MB
- MIME type
- (unknown)
- Detected type
- Win32 EXE
- SHA-256
- b789785c7fc746504b2ffa45c6f5ede63ad199eed400624b7faf8ff27e8cb271
- MD5
- f9a81f54651883068ddb6c9502a83869
- SHA-1
- 5f1e8f3e21da7da41f14ac12d6496418cd7af657
- PE imphash
- 62fa08f7e2a993a36770323113930fbf
- First seen (VT)
- 9/7/2023, 11:57:06 AM
- Last analysis (VT)
- 6/5/2026, 2:56:16 PM
- First scan (MalwareTips)
- 7/12/2026, 6:11:17 AM
- Last scan (MalwareTips)
- 7/12/2026, 6:11:17 AM
- Code signer
- Kaspersky Lab JSCinvalid
Safety FAQ
Common questions about Setup.exe, answered from the scan data above.
- Setup.exe is suspicious — treat it as unsafe until you're sure. 1 of 75 antivirus engines flag it (family: zenpak), which isn't a strong consensus but is enough to be cautious. Don't run it unless you fully trust where it came from, and prefer downloading the software fresh from its official site.
- Setup.exe is a Windows executable program, about 4.2 MB. We identify a file by its cryptographic hash rather than its name, because the same filename can be reused by completely different files — the hash below is the reliable fingerprint.
- 1 of 75 antivirus engines flagged Setup.exe, 1 of them as outright malicious. A small number of detections can include false positives, so we weigh which engines flagged it and what else the file does, not just the raw count.
- Act quickly. 1) Disconnect the device from the internet to stop the malware communicating or spreading. 2) Run a full scan with reputable anti-malware software (such as Malwarebytes) and quarantine everything it finds. 3) Change your important passwords from a DIFFERENT, clean device — many threats log keystrokes or steal saved credentials. 4) If you bank or shop on this device, watch closely for fraud and alert your bank. 5) For a confirmed infection, the most reliable fix is to back up your personal files and reinstall the operating system for a clean start.
- To remove Setup.exe: 1) restart into Safe Mode (Safe Mode with Networking if you need to download a tool) so the malware doesn't auto-start. 2) Run a full scan with reputable anti-malware software and let it quarantine or delete the detections. 3) Delete the original Setup.exe file and empty the Recycle Bin/Trash. 4) Check your browser extensions, startup items, and scheduled tasks for anything unfamiliar. 5) Reboot and scan again to confirm it's gone. If detections keep coming back, a clean operating-system reinstall is the most dependable cure.
- Setup.exe is classified as a trojan — malware disguised as something harmless to trick you into running it. Engines attribute it to the zenpak family. Knowing the family matters because it tells you the likely impact — data theft, remote control, file encryption, or unwanted ads — and guides the cleanup.
- Setup.exe claims a signer of Kaspersky Lab JSC, but the signature is not verified — an unverified or broken signature can be forged, so it should not be trusted as proof of who made the file.
- The SHA-256 hash of Setup.exe is b789785c7fc746504b2ffa45c6f5ede63ad199eed400624b7faf8ff27e8cb271, and its MD5 is f9a81f54651883068ddb6c9502a83869. This hash is the file's unique fingerprint — two files with the same SHA-256 are identical. Use it to confirm you're looking at exactly this file (not just one with the same name) when comparing against antivirus databases or a download's published checksum.
- This report reflects the scan run on July 12, 2026. Because a file's hash never changes, the identity of Setup.exe is fixed — but antivirus coverage improves over time, so a file that looks clean today can pick up detections later (and vice-versa). If you need the latest picture, MalwareTips staff can re-run the analysis from scratch.
Reviews & malware reports(0)
Tell the community what you saw. Tag the sample — Trojan, Adware, False Positive — and share what the file did on your system. Your report helps confirm or dispute the AV verdict.