File scan report
Verdict Suspicious
Is driver_ booster_ setup. exe safe? Treat it as suspicious.
This unsigned Driver Booster installer is flagged by 4 of the 68 antivirus engines that checked it as a bundling or potentially unwanted program, and it matches several community…
Read the whole reasonShow less
Why Suspicious? 4 antivirus engines flag it and a community rule for known malware matched it.
Moderate evidence · More than one sign points to a problem, but nothing confirms it is harmful.
Avoid this unsigned copy and get the installer from the vendor's official site instead, checking for a valid signature. If you install it, decline any bundled offers and keep your antivirus 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
4 of 68 flagged
- Flagged 4
- No detection 64
- No result 7
- Code signing Unsigned
- Test run Completed
- First seen 24d 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
Two major antivirus engines and Malwarebytes label this installer a potentially unwanted or bundling program, and five community YARA rules matched it. It is unsigned, so there is no verified publisher behind it. The sandbox run showed ordinary installer activity and contact with IObit update servers, with no high-risk techniques.
4 of the 68 antivirus engines that checked it flagged the file, including DrWeb and GData among the major antivirus engines. Every label points to an unwanted program or a bundling installer rather than a named malware family. The executable carries no digital signature, which removes the strongest way to confirm it came from the claimed vendor. Five automatically generated community YARA rules matched it; they name no family, but nothing in the evidence counters them. On the other side, the combined sandbox verdict was clean, no injection target was recorded, and the network contacts were vendor update servers plus an IP-geolocation lookup. These signals together point to a potentially unwanted bundling installer rather than confirmed malware.
What We Detected
4 of the 68 antivirus engines that checked it flagged this installer. DrWeb reports Program.Unwanted.5065, GData reports Win32.Application.IObit.F, Malwarebytes reports PUP.Optional.BundleInstaller, and Palo Alto gives a generic machine-learning verdict. The file is unsigned. Five automatically generated community YARA rules matched it without naming a malware family. It was first seen on Oct 2, 2026, and has been submitted by 52 sources.
Threat Behavior
The combined sandbox verdict was clean. The installer unpacked its setup components to a temporary folder, as installers built this way normally do. It contacted update.iobit.com and aegis.iobit.com and queried ip-api.com for location data. No injection into other processes, persistence or high-risk techniques were recorded. Our host-reputation check found none of the contacted hosts malicious.
What To Do Now
Download Driver Booster only from the vendor's official site, and confirm the installer carries a valid digital signature before running it. If you run it, choose custom installation and decline any bundled offers. Keep your antivirus enabled throughout.
Where this verdict could be wrong2 caveats
- The combined sandbox verdict was clean and recorded no high-risk techniques, so this may simply be a bundled vendor installer rather than harmful code.
- The five matching community YARA rules are auto-generated and name no malware family, so they may be overmatching a common installer framework.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- The combined sandbox verdict was clean, with no high-risk techniques recorded
- Network contacts went to the vendor's update servers
- No packing or obfuscation was found in the executable
- Most major antivirus engines did not flag it
- Two major antivirus engines and Malwarebytes label it a potentially unwanted or bundling program
- The installer has no digital signature, so its publisher cannot be verified
- Five community malware-pattern rules matched the file
- It queries an IP-geolocation service during installation
6 sources checked · all complete. 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- 21sandbox rule tags
- 5spawned processes
- 6network contacts
- 14filesystem & 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: Ran commands or a script on the test computer.
Moderate concern: Checked whether it was running on a test computer.
Note: Read the user name of the 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 code injection, but no injected program 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
driver_booster_setup.exe
8731fcb399ad5bb375eb78c443f55dbfd20362cc2de30ab54fb7053f8a412ffe
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
driver_booster_setup.exe
"C:\Users\<USER>\Desktop\driver_booster_setup.exe"
Test run - Evidence 3 of 7: ProcessSeen in the test run
driver_booster_setup.tmp
"C:\Users\<USER>\AppData\Local\Temp\is-TDHLN.tmp\driver_booster_setup.tmp" /SL5="$6002C,33445181,139264,C:\Users\<USER>\Desktop\driver_booster_setup.exe"
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
driver_booster_setup.tmp
C:\Users\<USER>\AppData\Local\Temp\is-TDHLN.tmp\driver_booster_setup.tmp
Test run - Evidence 5 of 7: Written fileSeen in the test run
driver_booster_setup.tmp
C:\Users\<USER>\AppData\Local\Temp\is-HHOUR.tmp\driver_booster_setup.tmp
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
aegis.iobit.com
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
update.iobit.com
Contacted during the test run.
Test run - +1 more recorded observation
7 facts from the test run. See the full activity list.
Includes the sandbox verdicts, 21 mapped techniques, every process, file, registry and network entry and 4 dropped files.
Show the technical evidenceChapter 04
Technical details
4 of the 68 antivirus engines that checked it flag it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · all complete. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 4
- DrWeb (major engine)Program.Unwanted.5065
- GData (major engine)Win32.Application.IObit.F
- MalwarebytesPUP.Optional.BundleInstaller
- Paloaltogeneric.ml
File fingerprint
- Last analyzed
- Oct 16, 2026, 3:31 PM UTC
- SHA-256
8731fcb399ad5bb375eb78c443f55dbfd20362cc2de30ab54fb7053f8a412ffe- SHA-1
a095c00786e6ac58be8c8df54cc5e60e99ea4217- MD5
0cb7b65bab871e452da64b8a1e1de8ea
About this file
driver_booster_setup.exe is a Win32 EXE file of 34.2 MB.
- Type and size
- Win32 EXE · 34.2 MB
- Signer
- UnsignedNo code signature.
- First seen
- Oct 2, 2026On VirusTotal.
- Submitted by
- 52 distinct sources
- Packer
- None detected
- Entropy
- 5.66 of 8
First scanned Updated
Includes every engine result (75), 11 matched signature rules, PE section entropy and packers and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is driver_booster_setup.exe safe, or is it malware?
What is driver_booster_setup.exe?
How many antivirus engines detected driver_booster_setup.exe?
I already downloaded and installed driver_booster_setup.exe — what should I do?
What is the SHA-256 hash of driver_booster_setup.exe?
How up to date is this analysis of driver_booster_setup.exe?
Community
Member reviews and reports for this exact file hash.