MalwareTipsTools

File scan report

Verdict Malicious

Analyzed , 22 hours ago

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.

Don't run this file

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

  1. Don't run this file. Delete it, then empty the Recycle Bin.

If you already ran it

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

  2. If you typed passwords on the device after running it, change them from another device you trust.

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

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
FileUSB-Explorer.exe7.5 MBSHA-256 3f3e84744c41…d80e09
  • Code signing Unsigned
  • Test run Completed
  • First seen 1y ago
A sandbox test run rated its behaviour as malicious.

Chapter 02

Why we think so

5 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

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.

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.

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.

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

      USB-Explorer.exe

      3f3e84744c41d44ce8ec2cbbb6e97b837b5ea9e18cadee57781497ad23d80e09

      Uploaded file
  2. Processes

    What ran

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

      program.exe

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

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

    Created or changed

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

      VCRUNTIME140.dll

      C:\Users\<USER>\AppData\Local\Temp\_MEI58402\VCRUNTIME140.dll

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

      _bz2.pyd

      C:\Users\<USER>\AppData\Local\Temp\_MEI58402\_bz2.pyd

      Test run
    3. +1 more recorded observation
  4. Network

    Hosts contacted

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

      104.98.118.138

      Contacted during the test run.

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

      72.247.234.254

      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

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.

SourceStatusResultChecked
Antivirus enginesVirusTotal · 75 enginesCompleteRisk signal: 51 of 71 engines flagged it · 4 gave no result Details for antivirus engines
Sandbox runVirusTotal sandboxes · C2AE, CAPA, CAPE SandboxCompleteRisk signal: 8 runs: 1 malicious, 7 without a verdict Details for sandbox run
Contacted hostsMalwareTips URL scannerComplete10 contacted hosts checked Details for contacted hosts
Signature rulesYARAify community rules + MalwareTips rulesCompleteRisk signal: 4 MalwareTips behaviour rules Details for signature rules
Malware sample databaseabuse.ch MalwareBazaarCompleteNot listed
Known-software referenceCIRCL hashlookupCompleteNo match

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
43 more in the full engine list

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

Chapter 05

Questions & answers

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

Is USB-Explorer.exe a virus?
Yes. This copy of USB-Explorer.exe (SHA-256 3f3e8474…0e09) is malicious. Other files with the same name can be different, so check the hash. Don't run it. Delete it, then empty the Recycle Bin. 51 of the 71 antivirus engines that checked it flag it, some as Hesv. Antivirus engines classify it as a worm, which spreads itself to other computers. If you've already run it, see the steps below.
What is USB-Explorer.exe?
USB-Explorer.exe is a Windows program, about 7.5 MB. It carries no version information saying what it is or who made it. VirusTotal first saw it on Nov 11, 2024.
How many antivirus engines detected USB-Explorer.exe?
51 of the 71 antivirus engines that checked it flag USB-Explorer.exe, including Microsoft and Kaspersky. We weigh which engines flagged it and what else the scan found, not just the count. A sandbox test run also rated its behaviour as malicious.
What should I do if I already ran USB-Explorer.exe?
Act quickly. 1) Disconnect the device from the internet. 2) Run a full scan with your antivirus and let it remove what it finds. 3) Change your important passwords from another device you trust, starting with email and banking, and turn on two-step verification. 4) If you bank or shop on this device, watch your accounts and tell your bank about payments you don't recognise. 5) If the scan keeps finding it, back up your personal files and reinstall Windows.
How do I remove USB-Explorer.exe?
To remove USB-Explorer.exe: 1) run a full scan with your antivirus and let it remove what it finds. 2) Delete it, then empty the Recycle Bin. 3) Check Settings > Apps, your browser extensions, startup apps (Task Manager > Startup apps) and scheduled tasks for anything you don't recognise. 4) Restart and scan again. If it keeps coming back, scan from Safe Mode with Networking, or back up your files and reinstall Windows.
What kind of malware is USB-Explorer.exe?
Antivirus engines classify USB-Explorer.exe as a worm, which spreads itself to other computers. Engines attribute it to the Hesv family.
What is the SHA-256 hash of USB-Explorer.exe?
The SHA-256 fingerprint of USB-Explorer.exe is 3f3e84744c41d44ce8ec2cbbb6e97b837b5ea9e18cadee57781497ad23d80e09, and its MD5 is 41fe839aa45fe4b424451f38f0eb9167. 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 USB-Explorer.exe?
This report reflects the scan on Nov 1, 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.

Recent reports on other files with the same rating.

All file reports
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.