MalwareTips

File scan report

Scan another file

Verdict Suspicious

Analyzed , 1 month ago

Is setup.exe safe? Treat it as suspicious.

This installer has no antivirus detections and carries a valid but little-known signature, yet it silently downloads and installs a third-party Chromium-based browser called…

Read the whole reasonShow less

Why Suspicious? Silently installs a separate Chromium-based browser product using hidden install switches.

Limited evidence · One sign points to a problem; nothing else confirms it.

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

Avoid running this installer unless you deliberately want the DoxWave browser from a source you trust. If it is already installed, remove DoxWave and run a full scan with your security software enabled.

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

0 of 71 flagged

  • Flagged 0
  • No detection 71
  • No result 4
Filesetup.exe2.1 MBSHA-256 b98e86752887…2e1077
  • Code signing IZHAN INC
  • Test run Completed
  • First seen 6mo ago
None of the 71 antivirus engines that checked it flag it.

Chapter 02

Why we think so

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

MT AI Engine · Verdict analysis

The reasoning behind this verdict

Analyst conclusion

None of the 71 antivirus engines that checked it flagged this installer, and its signature from IZHAN INC verifies. However, the publisher has almost no history with us, and the sandbox runs show it silently downloading and installing a separate browser product while sending install data. That is typical of bundled potentially unwanted software rather than a clean, single-purpose setup.

Where this verdict could be wrong2 caveats
  • No antivirus engine flags the file, and the sandbox recorded no injection target, persistence or malicious verdict. The silent browser install may simply be aggressive but legitimate bundling.
  • A community annotation links the file to a cryptominer, but nothing in the scan evidence corroborates that claim.

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
  • 16sandbox rule tags
  • 11spawned processes
  • 9network contacts
  • 40filesystem & 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: Checked whether it was running on a test computer.

  • Note: Read the user name of 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.

  • Note: Read basic details of the test computer, such as its Windows version.

  • Note: Loaded extra code modules while running.

Sandbox labels we could not confirm (common in safe files too)

  • 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

      b98e867528875161cb888bc41b1c193efedef4716899754d66add032f82e1077

      Uploaded file

  2. Processes

    What ran

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

      identity_helper.exe

      "C:\Program Files (x86)\Microsoft\Edge\Application\122.0.2365.92\identity_helper.exe" --type=utility --utility-sub-type=winrt_app_id.mojom.WinrtAppIdService --lang=en-US --service-sandbox-type=none --no-appcompat-clear --mojo-platform-channel-handle=5724 --field-trial-handle=2116,i,14093811214933569450,8007852840420615121,262144 --variations-seed-version /prefetch:8

      Test run
    2. Evidence 3 of 7: ProcessSeen in the test run

      setup.exe

      "C:\Users\<USER>\Desktop\setup.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

      S-1-15-2-543634040-274359014-2226501544-3561766748-3991453649-3543631192-522786984

      \Device\NamedPipe\Sessions\1\AppContainerNamedObjects\S-1-15-2-543634040-274359014-2226501544-3561766748-3991453649-3543631192-522786984

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

      setup.tmp

      C:\Users\<USER>\AppData\Local\Temp\is-PUWJ82W2UP.tmp\setup.tmp

      Test run
    3. +1 more recorded observation

  4. Network

    Hosts contacted

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

      13.224.187.22

      Contacted during the test run.

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

      3.168.24.31

      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

None of the 71 antivirus engines that checked it flag it; signed by IZHAN INC.

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 enginesCompletePositive signal: 0 of 71 engines flagged it · 4 gave no result Details for antivirus engines
Sandbox runVirusTotal sandboxesCompleteRuntime behaviour was recorded Details for sandbox run
Contacted hostsMalwareTips URL scannerPartial2 of 9 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

File fingerprint

Last analyzed
Sep 4, 2026, 5:10 AM UTC
SHA-256
b98e867528875161cb888bc41b1c193efedef4716899754d66add032f82e1077
SHA-1
583673845aaba0aed5f8f19776f82feef0676d09
MD5
f88a465dcd96e6ea97d8e1d29fd0c34f

About this file

setup.exe is a Win32 EXE file of 2.1 MB.

Type and size
Win32 EXE · 2.1 MB
Signer
IZHAN INCValid code signature.
First seen
Apr 18, 2026On VirusTotal.
Submitted by
275 distinct sources
Packer
None detected
Entropy
8.00 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. No antivirus engine flags it; the caution comes from other evidence, such as who made it, how widely it is used or what it did in a test run. 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 2.1 MB. It carries no version information saying what it is or who made it. VirusTotal first saw it on Apr 18, 2026.
How many antivirus engines detected setup.exe?
None of the 71 antivirus engines that checked it flag setup.exe. A clean antivirus result is not proof of safety; the caution comes from other evidence, such as who made it, how widely it is used or what it did in a test run.
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?
Yes. setup.exe has a valid digital signature from IZHAN INC, which shows the file hasn't been changed since that publisher signed it. Malware is sometimes signed with stolen certificates, so a signature alone isn't proof of safety.
What is the SHA-256 hash of setup.exe?
The SHA-256 fingerprint of setup.exe is b98e867528875161cb888bc41b1c193efedef4716899754d66add032f82e1077, and its MD5 is f88a465dcd96e6ea97d8e1d29fd0c34f. 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 Sep 4, 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.