Is uTorrent Pro 3.6.0 Build 47008 Stable RePack (& Portable).exe safe?
Unsigned torrent client repack with tier-1 detections, LSASS access, and prior imphash matches flagged as suspicious or malicious.
Two tier-1 engines flagged the file; sandbox observed process injection and LSASS access. The sample is unsigned, carries a portable filename, and shares its imphash with previously suspicious or malicious files.
c076016b7aa7e607d6…808bcbf6e33bf8Recommended next actions
Before running
Do not run it until the source and publisher can be verified independently.
If you already ran it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the developer's official site or an official app store.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
Two tier-1 engines flagged the file; sandbox observed process injection and LSASS access. The sample is unsigned, carries a portable filename, and shares its imphash with previously suspicious or malicious files.
The combination of two tier-1 detections, seven offensive MITRE techniques, and five similar-hash verdicts that were suspicious or malicious outweighs the majority clean tier-1 results. Lack of code signing and the presence of a suspicious contacted host add further risk. No test-file label or confirmed hacktool consensus exists, so the file sits in mixed-signal territory rather than a definitive malicious classification.
What We Detected
3 of 75 engines flagged the sample. Fortinet and Ikarus (tier-1) reported malicious behavior and PUA.uTorrent respectively; Malwarebytes labeled it RiskWare.Keygen. The file is unsigned despite being an executable claiming to be uTorrent Pro RePack.
Threat Behavior
Sandbox execution recorded seven offensive MITRE techniques including T1055 (Process Injection) and LSASS memory access. Nineteen external IP addresses were contacted directly without domain names; one of those hosts (rutor.info) is already marked suspicious in our cache. Ten dropped children were inspected and none flagged malicious.
What To Do Now
Do not run the file. Obtain uTorrent only from the vendor’s official site and keep endpoint protection enabled. If this file is already on disk, submit it to your security vendor for further analysis.
Where this verdict could be wrong2 caveats
- communityComments[0] states the file is completely safe (multi-language claim) — single unverified annotation.
- engines.tier1ReportedClean=15 and engines.malicious=3 — majority of tier-1 engines did not flag.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 15 tier-1 engines reported clean
- No dropped malicious children
- No confirmed test-file or hacktool consensus
- Unsigned executable claiming to be commercial software
- Tier-1 detections for malicious behavior and PUA
- Sandbox observed LSASS access and process injection
- Imphash previously linked to suspicious or malicious samples
- Contact with a host already flagged suspicious
Treat as untrusted; obtain official software from the vendor and keep security software active.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete3 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial11 of 31 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete3 signature or behavior rules matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 32MITRE ATT&CK techniques
- 15spawned processes
- 31network contacts
- 35filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Created or modified a system service, which can keep code running.
High concern: Changed an auto-start location that can make code run after sign-in or restart.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Scans through your files and folders.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
uTorrent Pro 3.6.0 Build 47008 Stable RePack (& Portable).exe
c076016b7aa7e607d6de66ed3c046352a5ce7e1fcb055a07aa808bcbf6e33bf8
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
C:\Windows\system32\lsass.exe
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\file.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
file.tmp
C:\Users\<USER>\AppData\Local\Temp\is-HT4QG.tmp\file.tmp
04Isolated runtime analysis - Written fileObserved
_setup64.tmp
C:\Users\<USER>\AppData\Local\Temp\is-KVML6.tmp\_isetup\_setup64.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostDerived
rutor.info
Saved reputation verdict: suspicious.
06Contacted-host cross-check - Contacted hostObserved
20.99.186.246
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- 20.99.186.246
- 192.229.211.108
- 23.53.122.135
- 20.99.133.109
- 20.99.185.48
- 20.99.184.37
- 23.216.147.64
- 20.69.140.28
- 67.215.246.10
- 82.221.103.244
- http://i-29.b-47008.ut.bench.utorrent.com/e?i=29
- http://i-30.b-47008.ut.bench.utorrent.com/e?i=30
- http://i-43.b-47008.ut.bench.utorrent.com/e?i=43
- http://i-21.b-47008.ut.bench.utorrent.com/e?i=21
- http://i-32.b-47008.ut.bench.utorrent.com/e?i=32
- http://apps.bittorrent.com/utorrent-onboarding/player.btapp
- C:\Users\<USER>\AppData\Local\Temp\is-HT4QG.tmp\file.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-KVML6.tmp\_isetup\_setup64.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-KVML6.tmp\_isetup\_shfoldr.dll
- C:\Users\<USER>\AppData\Local\Temp\is-KVML6.tmp\_isetup\_iscrypt.dll
- C:\Users\<USER>\AppData\Local\Temp\is-KVML6.tmp\iswin7logo.dll
- C:\Users\<USER>\AppData\Roaming\uTorrent\is-IMTSM.tmp
- C:\Users\<USER>\AppData\Roaming\uTorrent\is-QNGLA.tmp
- C:\Users\<USER>\AppData\Roaming\uTorrent\is-PJVGQ.tmp
- C:\Users\<USER>\AppData\Roaming\uTorrent\is-RA6RH.tmp
- C:\Users\<USER>\AppData\Roaming\uTorrent\is-QA4NC.tmp
- cversions.3.m
- Local\RstrMgr3887CAB8-533F-4C85-B0DC-3E5639F8D511
- Local\RstrMgr-3887CAB8-533F-4C85-B0DC-3E5639F8D511-Session0000
- \Sessions\1\BaseNamedObjects\Local\RstrMgr3887CAB8-533F-4C85-B0DC-3E5639F8D511
- \Sessions\1\BaseNamedObjects\Local\RstrMgr-3887CAB8-533F-4C85-B0DC-3E5639F8D511-Session0000
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 7be7632ff5119cb20101…76b725Never scannednever seen before
- 1a696122e625e5a5edf3…1b39beNever scannednever seen before
- 2eab87471df45e97e4bc…d17d1aNever scannednever seen before
- a4c86fc4836ac728d7bd…95fd81Never scannednever seen before
- 9884e9d1b4f8a873ccbd…360d87Never scannednever seen before
- 2f6294f9aa09f59a574b…a0f8fcNever scannednever seen before
- 196390762f6393024e0c…e45cb5Never scannednever seen before
- 1a74639f42b0011890c2…a24a4aNever scannednever seen before
- 0a1913a9b5c8601e7042…72857cNever scannednever seen before
- 73b4b82f590e19a53507…520fc9Never scannednever seen before
Servers this file contacts
This file contacts 1 host we've flagged suspicious in our own URL scanner.
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 3rule hits recorded
- 3 / 75engines flagged
- 68sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
3 of 75 antivirus engines flagged the file, including Fortinet and Ikarus.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 73 times from 68 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: uTorrent Pro 3.6.0 Build 47008 Stable RePack (& Portable).exe — c076016b7aa7e607d6de66ed3c046352a5ce7e1fcb055a07aa808bcbf6e33bf8
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — C:\Windows\system32\lsass.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\<USER>\Desktop\file.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: file.tmp — C:\Users\<USER>\AppData\Local\Temp\is-HT4QG.tmp\file.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: _setup64.tmp — C:\Users\<USER>\AppData\Local\Temp\is-KVML6.tmp\_isetup\_setup64.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: rutor.info — Saved reputation verdict: suspicious.
ProvenanceDerivedSourceContacted-host cross-checkObserved at - 10
Contacted host: 20.99.186.246 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: hacktool
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
EvidenceC:\Windows\system32\lsass.exeSandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.
EvidenceC:\Windows\system32\lsass.exeThe sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence20.99.186.246 · 192.229.211.108 · 23.53.122.135
3 of 75 engines flagged this file
View all 75 engine results
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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- uTorrent Pro 3.6.0 Build 47008 Stable RePack (& Portable).exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 34.2 MB
- Last analyzed
- Sep 7, 2026, 12:23 PM UTC
c076016b7aa7e607d6de66ed3c046352a5ce7e1fcb055a07aa808bcbf6e33bf8Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't run it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source. Get a fresh copy from the developer's official site or an official app store.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is this file safe, or is it malware?
What is this file?
How many antivirus engines detected this file?
I already downloaded and ran this file — what should I do?
How do I remove this file?
What kind of malware is this file?
What is the SHA-256 hash of this file?
How up to date is this analysis of this file?
Community
Member reviews and reports for this exact file hash.