File scan report
Verdict Suspicious
Is setup.
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.
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
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
0 of 71 flagged
- Flagged 0
- No detection 71
- No result 4
- Code signing IZHAN INC
- Test run Completed
- First seen 6mo ago
Chapter 02
Why we think so
4 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
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.
Antivirus results are clean: 0 of the 71 antivirus engines that checked it flagged the file, including all 18 major antivirus engines that reported. The code signature from IZHAN INC is valid, but this signer has only one prior sample in our records and is not a recognised publisher. In the sandbox runs, the Inno Setup installer launched a DoxWave component with silent switches. That component unpacked and installed a Chromium-based browser, downloaded a further installer from the DoxWave server and reported install statistics. We saw no high-risk techniques, no named injection target and no persistence entries. One community note mentions a cryptominer, but none of the scan evidence supports it. Overall, the file looks like a silent bundler of unrequested software rather than confirmed malware.
What We Detected
None of the 71 antivirus engines that checked it flagged this installer. It carries a valid code signature from IZHAN INC, but that publisher has almost no history with us. A community annotation links the hash to a cryptominer, but no engine, rule or sandbox result corroborates this.
Threat Behavior
The sandbox runs show an Inno Setup installer that silently launches a DoxWave component. That component installs a Chromium-based browser, downloads an additional installer from the vendor's server and sends install data. The silent install of a second product is the main concern. We observed no injection into other processes and no persistence entries. Our host-reputation check covered only part of the network contacts.
What To Do Now
Run this file only if you knowingly wanted the DoxWave browser from a trusted source. If a different program you expected installed DoxWave instead, uninstall it from Windows Settings and run a full scan with your security software, keeping that protection enabled.
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.
- None of the 71 antivirus engines that checked it flagged the file
- Valid, intact code signature from IZHAN INC
- No high-risk techniques, injection targets or persistence were recorded in the sandbox runs
- Seen from about 275 distinct sources over six months
- Silently installs a separate Chromium-based browser product using hidden install switches
- Downloads an additional installer from the internet during setup and sends install data
- The signing publisher is little known and has almost no history in our records
- A community annotation associates the file with a cryptominer, though nothing in the scan evidence confirms 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.
- 1
Input file
The submitted object
- Evidence 1 of 7: FileSeen in the test run
setup.exe
b98e867528875161cb888bc41b1c193efedef4716899754d66add032f82e1077
Uploaded file
- 2
Processes
What ran
- 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 - Evidence 3 of 7: ProcessSeen in the test run
setup.exe
"C:\Users\<USER>\Desktop\setup.exe"
Test run - +1 more recorded observation
- 2
Files
Created or changed
- 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 - 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 - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
13.224.187.22
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
3.168.24.31
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
16MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1027· Obfuscated code
- T1027.002· Obfuscated code
- T1033· Reads user info
- T1036
- T1055· Process injection
- T1070· Covers its tracks
- T1071· Application protocol
- T1082· System recon
- T1106
- T1129· Loads modules
- T1485
- T1497· Sandbox evasion
- T1548
- T1562· Disables security
- T1562.001· Disables security
- T1573
Observed activity
Processes started
11Programs the file ran, with their command lines.
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:8setup.exe"C:\Users\<USER>\Desktop\setup.exe"setup.tmp"C:\Users\<USER>\AppData\Local\Temp\is-PUWJ82W2UP.tmp\setup.tmp" /SL5="$160198,892928,892928,C:\Users\<USER>\Desktop\setup.exe"DoxWave.exe"C:\Users\<USER>\AppData\Local\Temp\is-IP4S5N9RMD.tmp\DoxWave.exe" /S /silentsetup.exe"C:\Users\<USER>\AppData\Local\Temp\is-IP4S5N9RMD.tmp\CR_60DE1.tmp\setup.exe" --install-archive="C:\Users\<USER>\AppData\Local\Temp\is-IP4S5N9RMD.tmp\CR_60DE1.tmp\CHROME.PACKED.7Z" /S /silentsetup.exeC:\Users\<USER>\AppData\Local\Temp\is-IP4S5N9RMD.tmp\CR_60DE1.tmp\setup.exe --type=crashpad-handler /prefetch:4 --monitor-self-annotation=ptype=crashpad-handler "--database=C:\Users\<USER>\AppData\Local\DoxWave\DoxWave\User Data\Crashpad" --annotation=plat=Win32 --annotation=prod=DoxWave --annotation=ver=143.0.7488.0 "--attachment=C:\Program Files (x86)\chromium_installer.log" --initial-client-data=0x36c,0x370,0x374,0x348,0x378,0xbbc804,0xbbc810,0xbbc81c
Show all 11 entries for processes started
setup.exe"C:\Users\<USER>\AppData\Local\Temp\is-IP4S5N9RMD.tmp\CR_60DE1.tmp\setup.exe" --verbose-logging --create-shortcuts=0 --install-level=0setup.exeC:\Users\<USER>\AppData\Local\Temp\is-IP4S5N9RMD.tmp\CR_60DE1.tmp\setup.exe --type=crashpad-handler /prefetch:4 --monitor-self-annotation=ptype=crashpad-handler "--database=C:\Users\<USER>\AppData\Local\DoxWave\DoxWave\User Data\Crashpad" --annotation=plat=Win32 --annotation=prod=DoxWave --annotation=ver=143.0.7488.0 "--attachment=C:\Program Files (x86)\chromium_installer.log" --initial-client-data=0x378,0x37c,0x380,0x350,0x384,0xbbc804,0xbbc810,0xbbc81cchrome.exe"C:\Users\<USER>\AppData\Local\DoxWave\DoxWave\Application\chrome.exe" --from-installerUpdaterSetup.exe"C:\Users\<USER>\AppData\Local\DoxWave\DoxWave\Application\UpdaterSetup.exe" --installchrome.exeC:\Users\<USER>\AppData\Local\DoxWave\DoxWave\Application\chrome.exe --type=crashpad-handler "--user-data-dir=C:\Users\<USER>\AppData\Local\DoxWave\DoxWave\User Data" /prefetch:4 --monitor-self-annotation=ptype=crashpad-handler "--database=C:\Users\<USER>\AppData\Local\DoxWave\DoxWave\User Data\Crashpad" --annotation=plat=Win32 --annotation=prod=DoxWave --annotation=ver=143.0.7488.0 --initial-client-data=0x220,0x248,0x24c,0x224,0x250,0x70d15cdc,0x70d15ce8,0x70d15cf4
Network contacts
99 hosts, listed as 7 addresses, 3 links. Links show the host and path only.
- IP address
13.224.187.22 - IP address
3.168.24.31 - IP address
18.238.152.24 - IP address
13.107.213.38 - IP address
150.171.74.13 - IP address
142.251.190.132
Show all 10 entries for network contacts
- IP address
13.107.246.38 - URL
https://telemetry.doxwave.com/api/install/start - URL
https://serve.doxwave.com/download/doxwave/mini_installer.exe - URL
https://telemetry.doxwave.com/api/stats
Files
30Files the file created, changed or deleted.
- Written
\Device\NamedPipe\Sessions\1\AppContainerNamedObjects\S-1-15-2-543634040-274359014-2226501544-3561766748-3991453649-3543631192-522786984 - Written
C:\Users\<USER>\AppData\Local\Temp\is-PUWJ82W2UP.tmp\setup.tmp - Written
C:\Users\<USER>\AppData\Local\Temp\is-IP4S5N9RMD.tmp\_isetup\_setup64.tmp - Written
C:\Users\<USER>\AppData\Local\Microsoft\Windows\Explorer\iconcache_idx.db - Written
C:\Users\<USER>\AppData\Local\Microsoft\Windows\Explorer\iconcache_256.db - Written
C:\Users\<USER>\AppData\Local\Microsoft\Windows\Explorer\iconcache_48.db
Show all 30 entries for files
- Written
C:\Users\<USER>\AppData\Local\Temp\is-IP4S5N9RMD.tmp\CR_60DE1.tmp\CHROME.PACKED.7Z - Written
C:\Users\<USER>\AppData\Local\Temp\is-IP4S5N9RMD.tmp\CR_60DE1.tmp\SETUP.EX_ - Written
C:\Users\<USER>\AppData\Local\Temp\is-IP4S5N9RMD.tmp\CR_60DE1.tmp\setup.exe - Written
C:\Program Files (x86) - Written
C:\Program Files (x86)\chromium_installer.log - Written
C:\Users\<USER>\AppData\Local\DoxWave\DoxWave\User Data\Crashpad\settings.dat - Written
C:\Users\<USER>\AppData\Local\DoxWave\DoxWave\Temp\source6816_163291092\chrome.7z - Written
C:\Users\<USER>\AppData\Local\DoxWave\DoxWave\Temp\source6816_163291092\Chrome-bin\143.0.7488.0\143.0.7488.0.manifest - Written
C:\Users\<USER>\AppData\Local\DoxWave\DoxWave\Temp\source6816_163291092\Chrome-bin\143.0.7488.0\chrome.dll - Deleted
C:\Users\<USER>\AppData\Local\Temp\is-IP4S5N9RMD.tmp\DoxWave.exe - Deleted
C:\Users\<USER>\AppData\Local\Temp\is-IP4S5N9RMD.tmp\_isetup - Deleted
C:\Users\<USER>\AppData\Local\Temp\is-IP4S5N9RMD.tmp\CR_60DE1.tmp\SETUP.EX_ - Deleted
C:\Users\<USER>\AppData\Local\Temp\is-IP4S5N9RMD.tmp\CR_60DE1.tmp\CHROME.PACKED.7Z - Deleted
C:\Users\<USER>\AppData\Local\Temp\is-IP4S5N9RMD.tmp\CR_60DE1.tmp\setup.exe - Deleted
C:\Users\<USER>\AppData\Local\DoxWave\DoxWave\Temp\source6816_163291092\chrome.7z - Deleted
\Device\HarddiskVolume2\Users\<USER>\AppData\Local\DoxWave\DoxWave\Temp\source6816_163291092\chrome.7z - Deleted
C:\Users\<USER>\AppData\Local\DoxWave\DoxWave\Temp\source6816_163291092\Chrome-bin\143.0.7488.0\143.0.7488.0.manifest - Deleted
\Device\HarddiskVolume2\Users\<USER>\AppData\Local\DoxWave\DoxWave\Temp\source6816_163291092\Chrome-bin\143.0.7488.0\143.0.7488.0.manifest - Deleted
C:\Users\<USER>\AppData\Local\DoxWave\DoxWave\Temp\source6816_163291092\Chrome-bin\143.0.7488.0\chrome.dll - Deleted
\Device\HarddiskVolume2\Users\<USER>\AppData\Local\DoxWave\DoxWave\Temp\source6816_163291092\Chrome-bin\143.0.7488.0\chrome.dll - Deleted
C:\Users\<USER>\AppData\Local\DoxWave\DoxWave\Temp\source6816_163291092\Chrome-bin\143.0.7488.0\chrome_100_percent.pak - Deleted
\Device\HarddiskVolume2\Users\<USER>\AppData\Local\DoxWave\DoxWave\Temp\source6816_163291092\Chrome-bin\143.0.7488.0\chrome_100_percent.pak - Deleted
C:\Users\<USER>\AppData\Local\DoxWave\DoxWave\Temp\source6816_163291092\Chrome-bin\143.0.7488.0\chrome_200_percent.pak - Deleted
\Device\HarddiskVolume2\Users\<USER>\AppData\Local\DoxWave\DoxWave\Temp\source6816_163291092\Chrome-bin\143.0.7488.0\chrome_200_percent.pak
Registry and auto-start
3Settings the file changed, including ways to start again after a restart.
- Deleted
HKEY_CURRENT_USER\SOFTWARE\Microsoft\RestartManager\Session0000\Sequence - Deleted
HKEY_CURRENT_USER\SOFTWARE\Microsoft\RestartManager\Session0000\Owner - Deleted
HKEY_CURRENT_USER\SOFTWARE\Microsoft\RestartManager\Session0000\SessionHash
Mutexes
10Named locks a program uses so only one copy runs; malware families often reuse them.
Global\ChromeSetupMutex_2473026916Global\ChromeSetupExitEventMutex_2473026916TaskbarPinListMutexGlobal\SyncRootManagercversions.3.mLocal\ChromeProcessSingletonStartup!
Show all 10 entries for mutexes
__OMADM_NAMED_MUTEX__Global\OneSettingQueryMutex+compat+encapsulation\Sessions\1\BaseNamedObjects\Local\RstrMgr3887CAB8-533F-4C85-B0DC-3E5639F8D511\Sessions\1\BaseNamedObjects\Local\RstrMgr-3887CAB8-533F-4C85-B0DC-3E5639F8D511-Session0000
Sandbox background — not the file
4The analysis machine's own processes and connections, recorded in every run.
- VM process
Explorer.EXEC:\Windows\Explorer.EXE - 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
Files this sample writes at runtime
This file drops 9 children at runtime. None are currently flagged malicious in our cache. 9 have no saved verdict and were not checked; that is missing coverage, not a finding.
- c519d93514d3672ffb2a…99b159Not checkedno saved verdict
- 92db4443187c72794cfb…bd1b4aNot checkedno saved verdict
- bd50bf419dcf9bab3297…4b2511Not checkedno saved verdict
- 82ffb94eb3aa4ed2e1cc…0f5be4Not checkedno saved verdict
- 64920912faf5f77451e4…4fbe4fNot checkedno saved verdict
- 2354b257fdbed9193c43…e4be96Not checkedno saved verdict
- fd668d6edcf6b6cc176e…59550eNot checkedno saved verdict
- d828a61c56ac02f68860…a69bc6Not checkedno saved verdict
- 69cbb0502e9c385d2eda…af1c46Not checkedno saved verdict
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.
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
Antivirus consensus
0 of 71 engines flagged this file
4 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-118 engines0flagged
- Tier-236 engines0flagged
- Low-trust17 engines0flagged
View all 75 engine results
- 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
- IkarusClean
- JiangminClean
- 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.