File scan report
Verdict Malicious
Is USB- Explorer. exe safe? No, we rate this exact file malicious.
Fifty-one of the 71 antivirus engines that checked it flagged this unsigned executable, with major agreement on Hesv and sandbox evidence of persistent startup execution.
Read the whole reasonShow less
Strong evidence · Two or more major antivirus engines agree.
If you already ran it, follow the steps below.
What to do now4 steps
This file is harmful. Don't run it, and remove it.
If you haven't run it
Don't run this file. Delete it, then empty the Recycle Bin.
If you already ran it
Disconnect the device from the internet, then run a full antivirus scan. Microsoft Defender Offline (Windows Security > Virus & threat protection > Scan options) also finds malware that hides while Windows runs.
If you typed passwords on the device after running it, change them from another device you trust.
If the scan keeps finding it, or the device still acts strangely, scan again with a second-opinion scanner from another company; if that doesn't fix it, back up your personal files and reinstall Windows.
If you already ran it, do these in order.
If you opened or installed it
Avoid banking and sign-ins on that device until it is clean. These free MalwareTips guides walk you through it.
- Trojan removal guideClear steps for Windows, Mac and Android. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Antivirus results
51 of 71 flagged
- Flagged 51
- No detection 20
- No result 4
- Code signing Unsigned
- Test run Completed
- First seen 1y ago
Chapter 02
Why we think so
5 points against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
The detection pattern strongly identifies a Hesv-associated USB worm: 51 of the 71 antivirus engines that checked it flagged it, including 13 major antivirus engines. Sandbox execution also produced a malicious combined verdict and showed the program establishing Windows startup persistence for a copied executable.
The antivirus evidence is extensive: 51 of the 71 antivirus engines that checked it flagged the executable, representing 39 independent detection sources. Three major antivirus engines agree on Hesv, while several others identify a USB worm or related trojan behavior. Sandbox execution corroborated those findings by recording a malicious combined verdict and a Windows Run entry that launches GPLControl.exe at sign-in. The executable is unsigned and packaged with PyInstaller, which adds no trustworthy publisher attribution. Although it has broad submission history and no known-malicious contacted host was identified, those points do not plausibly outweigh the family consensus and concrete persistence behavior.
What We Detected
Fifty-one of the 71 antivirus engines that checked it flagged the executable, including 13 major antivirus engines and 39 independent detection sources. Kaspersky and Ikarus identify the Hesv family, while BitDefender, ESET-NOD32, and other engines describe USB-worm or worm-related activity. The file has no digital signature that could establish its publisher.
Threat Behavior
Sandbox execution produced a malicious combined verdict. It also recorded the executable creating a Windows Run entry for GPLControl.exe, causing that program to start when the user signs in. This concrete persistence artefact supports the engine findings. The network entries shown in the sandbox summary were identified as analysis-system background activity rather than sample-originated contacts.
What To Do Now
Do not run the executable or connect removable drives to an affected system. Keep security software enabled, let your antivirus remove the file, scan attached USB devices and the host, and inspect Windows startup entries for the GPLControl component.
Where this verdict could be wrong3 caveats
- The file has substantial distribution history, with 142 distinct submitters and a first-seen date of Nov 11, 2024.
- The completed host-reputation cross-check found no known-malicious or suspicious host among the inspected contacts; the listed contacts were identified as analysis-system background traffic.
- One file with the same import-table fingerprint previously received a safe result, but it had a different claimed signer and only 2/74 detections, making the resemblance weak.
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 file has been submitted by 142 distinct sources and was first seen on Nov 11, 2024.
- The inspected network contacts contained no known-malicious or suspicious host, and the recorded contacts were attributed to analysis-system background activity.
- One inspected file it created matched a known-software reference entry.
- Fifty-one of the 71 antivirus engines that checked it detected the executable.
- Thirteen major antivirus engines flagged it, with three agreeing on the Hesv family.
- Sandbox execution recorded a malicious combined verdict.
- The program created a Windows startup entry for GPLControl.exe.
- The executable is unsigned and bundled with PyInstaller.
6 sources checked · all complete. See every source
Chapter 03
What it did in our test
It ran in 8 isolated tests; 1 test environment rated what it did as risky.
Test run summary
Capture complete- 8isolated sandbox runs
- 21sandbox rule tags
- 15spawned processes
- 2network contacts
- 30filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Set itself to start automatically after a restart.
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: Unpacked hidden content while it ran.
Moderate concern: Hid files or windows 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 changing how Windows loads code; nothing confirms it.
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.
Threat context
How worms spread
A worm copies itself from one computer to the next, across a network, through shared drives or on USB sticks, without anyone doing anything.
Bottom line:One infected machine can quickly reach every device around it.
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
USB-Explorer.exe
3f3e84744c41d44ce8ec2cbbb6e97b837b5ea9e18cadee57781497ad23d80e09
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
program.exe
"C:\Users\<USER>\Desktop\program.exe"
Test run - Evidence 3 of 7: ProcessSeen in the test run
cmd.exe
C:\Windows\system32\cmd.exe /c "REG ADD HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Run /v GPLControl /t REG_SZ /d C:\Users\Public\Libraries\GPLControl.exe /f"
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
VCRUNTIME140.dll
C:\Users\<USER>\AppData\Local\Temp\_MEI58402\VCRUNTIME140.dll
Test run - Evidence 5 of 7: Written fileSeen in the test run
_bz2.pyd
C:\Users\<USER>\AppData\Local\Temp\_MEI58402\_bz2.pyd
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
104.98.118.138
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
72.247.234.254
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 9 dropped files.
Show the technical evidenceChapter 04
Technical details
51 of the 71 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 51
- Avast (major engine)Other:Malware-gen [Trj]
- AVG (major engine)Other:Malware-gen [Trj]
- Avira (major engine)TR/Malware
- BitDefender (major engine)Gen:Variant.USBWorm.1
- DrWeb (major engine)Trojan.MulDrop32.31459
- Emsisoft (major engine)Gen:Variant.USBWorm.1 (B)
- ESET-NOD32 (major engine)Python/Agent.H worm
- F-Secure (major engine)Trojan.TR/Malware
File fingerprint
- Last analyzed
- Nov 1, 2026, 4:55 AM UTC
- SHA-256
3f3e84744c41d44ce8ec2cbbb6e97b837b5ea9e18cadee57781497ad23d80e09- SHA-1
3903b48194380b87e6cac0ae96d4c954cfee7440- MD5
41fe839aa45fe4b424451f38f0eb9167
About this file
USB-Explorer.exe is a Win32 EXE file of 7.5 MB.
- Type and size
- Win32 EXE · 7.5 MB
- Signer
- UnsignedNo code signature.
- First seen
- Nov 11, 2024On VirusTotal.
- Submitted by
- 142 distinct sources
- Packer
- PyInstaller (DetectItEasy packer)Packing hides code; legitimate installers use it too.
- Entropy
- 6.28 of 8
First scanned
Includes every engine result (75), 4 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 8 questions people ask most about this file.
Is USB-Explorer.exe a virus?
What is USB-Explorer.exe?
How many antivirus engines detected USB-Explorer.exe?
What should I do if I already ran USB-Explorer.exe?
How do I remove USB-Explorer.exe?
What kind of malware is USB-Explorer.exe?
What is the SHA-256 hash of USB-Explorer.exe?
How up to date is this analysis of USB-Explorer.exe?
Community
Member reviews and reports for this exact file hash.