File scan report
Verdict Safe
Is uTorrent Pro 3.
Only Bkav flagged this widely submitted executable with a generic label; higher-trust engines and checked runtime indicators supplied no corroborating evidence.
Read the whole reasonShow less
Strong evidence · Widely seen for a long time, and nothing harmful found.
Good practice2 tips
We found nothing harmful in this file.
Run it only if it came from the developer's own website or an official app store.
Keep your antivirus and Windows updates switched on.
No scanner can promise a file is 100% safe.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
1 of 72 flagged
- Flagged 1
- No detection 71
- No result 4
- Code signing Unsigned
- Test run Completed
- First seen 1y ago
Chapter 02
Why we think so
4 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Only 1 of the 72 antivirus engines that checked it flagged the executable, using Bkav's generic W32.AIDetectMalware label; higher-trust engines did not flag it.
The antivirus result is dominated by a lone generic Bkav detection, while none of the higher-trust engines flagged the file. It has been submitted by 175 sources since Nov 23, 2024, providing a meaningful distribution-history anchor. The sandbox runs recorded no named injection target or other high-risk technique with a supporting artefact; the bare and mappings do not establish those actions. Reputation checks covering the observed non-background hosts found no malicious or suspicious result, and no inspected child was identified as harmful. The main cautions are that this is an unsigned third-party repack and its bytes were not available for our static analysis.
What We Detected
Only 1 of the 72 antivirus engines that checked it flagged the executable. Bkav reported the generic label W32.AIDetectMalware, while the higher-trust engines did not flag it and no malware family was identified.
Threat Behavior
The sandbox runs did not record a named process-injection target or another corroborated high-risk technique. T1055 and T1562.001 appeared only as unsupported mappings, which do not demonstrate injection or security-tool tampering. Reputation checks covered the observed non-background hosts and found no malicious or suspicious result, while no inspected file it created was identified as harmful.
What To Do Now
The isolated detection is most consistent with a false positive, but this remains an unsigned third-party repack rather than a publisher-verified installer. Prefer an official release channel, keep security software enabled, and verify the file hash before use.
Where this verdict could be wrong3 caveats
- The executable is unsigned, so no verified publisher identity supports the claimed software origin.
- Five files built with the same import table previously received cautious assessments, although none had a matching signer and such construction-level matches can collide across unrelated installers.
- No completed examination of the uploaded bytes is available, so bundled contents were not independently inspected.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Only 1 of the 72 antivirus engines that checked it flagged the file, and the detection was a generic label from a less reliable engine.
- None of the higher-trust antivirus engines flagged the executable.
- The file has been submitted 255 times by 175 sources and was first seen on Nov 23, 2024.
- The sandbox runs recorded no named injection target or corroborated high-risk technique.
- Checks of the observed non-background hosts found no malicious or suspicious reputation, and no inspected child was identified as harmful.
- The executable is unsigned, so its publisher and claimed origin cannot be authenticated.
- It is presented as a third-party repack and portable build rather than a publisher-verified installer.
- The uploaded bytes were not available for our static analysis, so bundled components were not independently inspected.
- Five construction-level matches received cautious prior assessments, though they do not identify the same publisher or content.
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- 38sandbox rule tags
- 13spawned processes
- 11network contacts
- 37filesystem & mutex artifacts
Includes 38 mapped techniques, every process, file, registry and network entry and 10 dropped files.
Show the technical evidenceChapter 04
Technical details
1 of the 72 antivirus engines that checked it flags it; no publisher signature.
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.
Engines that flagged it 1
The saved verdict treats these detections as likely false positives.
- BkavW32.AIDetectMalware
File fingerprint
- Last analyzed
- Sep 7, 2026, 12:26 PM UTC
- SHA-256
509f9575f36f8811d98eebe9c64a01553eec220a0be9b63fc0e81b08df31d261- SHA-1
859f6e0e2eea34f29c697b5a40f5779313357840- MD5
a5750a5f4938741e7c561f15e74d9c0c
About this file
uTorrent Pro 3.6.0 Build 47168 Stable RePack (& Portable) by Dodakaedr.exe is a Win32 EXE file of 37.6 MB.
- Type and size
- Win32 EXE · 37.6 MB
- Signer
- UnsignedNo code signature.
- First seen
- Nov 23, 2024On VirusTotal.
- Submitted by
- 175 distinct sources
- Packer
- None detected
- Entropy
- 8.00 of 8
First scanned Updated
Verdict history
- Suspicious
- Safeafter a re-check of the saved evidence
Ratings change when antivirus engines, our checks or MalwareTips staff learn more about a file.
Includes every engine result (76), 1 matched signature rule, 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 this file safe?
What is this file?
How many antivirus engines detected this file?
What is the SHA-256 hash of this file?
Is it safe to run this file?
How up to date is this analysis of this file?
Community
Member reviews and reports for this exact file hash.