MalwareTips

File scan report

Scan another file

Verdict Suspicious

Analyzed , 3 months ago

Is Setup.exe safe? Treat it as suspicious.

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.

Don't install it until you know where it came from

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

  1. Don't install it unless you're sure where it came from.

  2. Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.

  3. 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

  1. 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.

Paste this report's link in your topic so helpers can see what was found.

Why we think so

Share this file report

Setup.exe: Suspicious — MalwareTips file scan

The link always shows the latest result for this exact file (its SHA-256 fingerprint).

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
FileSetup.exe4.4 MBSHA-256 b789785c7fc7…8cb271
  • Code signing Signer not verified
  • Test run Completed
  • First seen 3y ago
1 of the 70 antivirus engines that checked it flags it (Jiangmin).

Chapter 02

Why we think so

2 points against it and 3 in its favour, checked against the scan evidence.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

Analyst conclusion

Prevalence is widely seen and long established but behaviour raises red flags on an otherwise quiet sample.

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.

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.

Seen in the test runWorked out from other results

  1. Input file

    The submitted object

    1
    1. Evidence 1 of 7: FileSeen in the test run

      Setup.exe

      b789785c7fc746504b2ffa45c6f5ede63ad199eed400624b7faf8ff27e8cb271

      Uploaded file

  2. Processes

    What ran

    2
    1. Evidence 2 of 7: ProcessSeen in the test run

      file.exe

      "C:\Users\<USER>\Desktop\file.exe"

      Test run
    2. 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
    3. +1 more recorded observation

  3. Files

    Created or changed

    2
    1. Evidence 4 of 7: Written fileSeen in the test run

      Temp

      C:\Users\<USER>\AppData\Local\Temp

      Test run
    2. Evidence 5 of 7: Written fileSeen in the test run

      Kaspersky Lab Setup Files

      C:\ProgramData\Kaspersky Lab Setup Files

      Test run
    3. +1 more recorded observation

  4. Network

    Hosts contacted

    2
    1. Evidence 6 of 7: Contacted hostSeen in the test run

      62.67.238.152

      Contacted during the test run.

      Test run
    2. Evidence 7 of 7: Contacted hostSeen in the test run

      4.28.136.57

      Contacted during the test run.

      Test run
    3. +1 more recorded observation

7 facts from the test run. See the full activity list.

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.

SourceStatusResultChecked
Antivirus enginesVirusTotal · 75 enginesCompleteWorth noting: 1 of 70 engines flagged it · 5 gave no result Details for antivirus engines
Sandbox runVirusTotal sandboxesCompleteRuntime behaviour was recorded Details for sandbox run
Contacted hostsMalwareTips URL scannerPartial1 of 19 contacted hosts were cross-checked; coverage is incomplete Details for contacted hosts
Signature rulesYARAify community rules + MalwareTips rulesComplete1 MalwareTips behaviour rule Details for signature rules
Malware sample databaseabuse.ch MalwareBazaarCompleteNot listed
Known-software referenceCIRCL hashlookupCompleteNo match

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

Chapter 05

Questions & answers

Short answers to the 7 questions people ask most about this file.

Is Setup.exe safe, or is it malware?
Setup.exe is rated Suspicious: some signs point to a problem, but nothing confirms it is harmful. 1 of the 70 antivirus engines that checked it flags it, most as zenpak. Don't install it unless you're sure where it came from. If you need the software, download a fresh installer from the developer's own website.
What is Setup.exe?
Setup.exe is a software installer, about 4.4 MB. It carries no version information saying what it is or who made it. VirusTotal first saw it on Sep 7, 2023.
How many antivirus engines detected Setup.exe?
1 of the 70 antivirus engines that checked it flags Setup.exe (Jiangmin). We weigh which engines flagged it and what else the scan found, not just the count.
I already downloaded and installed Setup.exe — what should I do?
No infection is confirmed: the rating is a caution, not a malware finding. 1) Check where it came from. If you can't confirm the source, delete it. 2) Run a full scan with your security software. 3) If the scan finds something, follow its removal steps and change passwords you typed on the device since then.
Is Setup.exe digitally signed?
It carries a signature in the name of Kaspersky Lab JSC that could not be verified. Malware sometimes copies or steals a company's signature, so this does not mean that company made it.
What is the SHA-256 hash of Setup.exe?
The SHA-256 fingerprint of Setup.exe is b789785c7fc746504b2ffa45c6f5ede63ad199eed400624b7faf8ff27e8cb271, and its MD5 is f9a81f54651883068ddb6c9502a83869. Two files with the same SHA-256 are identical, so use it to check you have exactly this file, not just one with the same name.
How up to date is this analysis of Setup.exe?
This report reflects the scan on Jul 12, 2026. A file's fingerprint never changes, but antivirus engines keep learning, so a rating can change later. To get a newer result, scan the file again: we refresh the antivirus results when the saved ones are out of date.
Chapter 06

Community

Member reviews and reports for this exact file hash.

Related file reports

Other files people checked with the same name. A matching name does not make two files the same: only the SHA-256 fingerprint identifies a file.

All file reports
Scan another
Check a different file
URL instead?
Check if a link is safe
This report and its SHA-256 fingerprint are public, so the next person who checks the same file gets an instant answer; documents and images are listed by type instead of their file name. A file we had not seen before is uploaded to VirusTotal, whose security partners and subscribers can download it; MalwareTips deletes its own copy after the scan. If you ran this file and are worried, scan your device with up-to-date security software.