Is qbittorrent_5.2.3_x64_setup.exe safe?
Unsigned NSIS installer shows sandbox process-injection and LSASS access plus three YARA hits, yet zero AV detections.
The file triggered sandbox heuristics for process injection and LSASS access, matched three community YARA rules, and shares an imphash with five prior suspicious samples. No antivirus engine flagged it, but the unsigned status and incomplete host-reputation check leave the risk unresolved.
ff508e2f912d59c9ea…8a7d7ad867ab2fRecommended next actions
Before installing
Do not install it until the source and publisher can be verified independently.
If you already installed it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Download a fresh installer 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.
The file triggered sandbox heuristics for process injection and LSASS access, matched three community YARA rules, and shares an imphash with five prior suspicious samples. No antivirus engine flagged it, but the unsigned status and incomplete host-reputation check leave the risk unresolved.
Zero detections across 75 engines including 17 tier-1 products weighs against malice, yet the sandbox recorded T1055 and LSASS activity that legitimate installers rarely perform. Three YARA rules fired, one of which targets code injection. The imphash matches five earlier files that our analysis also rated suspicious. Because the file is unsigned and contacted-host reputation data is missing, the evidence remains mixed.
What We Detected
75 engines scanned the 43 MB NSIS installer; none returned a malicious or suspicious label. Sandbox execution recorded process-injection (T1055) and token-manipulation (T1134) calls plus direct access to lsass.exe. Three YARA rules matched, including one that flags cross-process code injection.
Threat Behavior
The observed LSASS access and direct-IP contact are consistent with credential-dumping or C2 patterns, but the same actions can appear in heavily customized installers. No malicious child files were dropped and no tier-1 family consensus exists.
What To Do Now
Run the installer only in a controlled environment or obtain a code-signed build from the official qBittorrent project site. Keep endpoint protection enabled; do not disable real-time scanning to test the file.
Where this verdict could be wrong2 caveats
- YARAify NSIS rule is expected for a legitimate installer; does not prove malice.
- contactedHosts=null means no complete host-reputation result is available.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Zero detections from 75 engines including 17 tier-1 products
- Medium prevalence with thousands of prior submissions
- No malicious dropped children
- Sandbox observed LSASS access and process injection
- Three YARA rules triggered, one targeting code injection
- Unsigned executable
- Imphash shared with five prior suspicious samples
- Contacted-host reputation check incomplete
Treat as unverified; obtain a signed copy from the vendor or test in an isolated VM before trusting the file on production systems.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
Complete6 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
- 20MITRE ATT&CK techniques
- 10spawned processes
- 1network contacts
- 25filesystem & 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: Changed an auto-start location that can make code run after sign-in or restart.
High concern: Manipulated how the operating system loads code, which can redirect execution.
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
qbittorrent_5.2.3_x64_setup.exe
ff508e2f912d59c9eabaf03633ebacfd45c2049f38dcac027b8a7d7ad867ab2f
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\qbittorrent_5.2.3_x64_setup.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Program Files\qBittorrent\qbittorrent.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
nsqE705.tmp
C:\Users\<USER>\AppData\Local\Temp\nsqE705.tmp
04Isolated runtime analysis - Written fileObserved
UAC.dll
C:\Users\<USER>\AppData\Local\Temp\nslE735.tmp\UAC.dll
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
162.159.36.2
Contact observed during runtime.
06Isolated runtime analysis
6 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.
- 162.159.36.2
- C:\Users\<USER>\AppData\Local\Temp\nsqE705.tmp
- C:\Users\<USER>\AppData\Local\Temp\nslE735.tmp\UAC.dll
- C:\Users\<USER>\AppData\Roaming\qBittorrent\lockfile
- C:\Users\<USER>\AppData\Local\qBittorrent\logs\qbittorrent.log
- C:\Users\<USER>\AppData\Roaming\qBittorrent\qBittorrent_new.ini.hnfkrK
- C:\Users\<USER>\AppData\Local\Temp\nslE735.tmp\UAC.dll
- C:\Users\<USER>\AppData\Local\Temp\nslE735.tmp\
- C:\Users\<USER>\AppData\Roaming\qBittorrent\qBittorrent_new.ini.hnfkrK
- C:\Users\<USER>\AppData\Roaming\qBittorrent\qBittorrent.ini
- C:\Users\<USER>\AppData\Roaming\qBittorrent\qBittorrent_new.ini
- Local\SessionImmersiveColorMutex
Files this sample writes at runtime
This file drops 5 children at runtime. None are currently flagged malicious in our cache.
- a1644158fd6e57284f66…f38e64Never scannednever seen before
- 2f7f8fc05dc4fd0d5cda…52dc08Never scannednever seen before
- b2eb1b1c6ef3b02d036f…a15491Never scannednever seen before
- dde3f3d0149526a0df65…e0d7acNever scannednever seen before
- 4cf25411f28f639f7215…2d5b7eNever scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 6rule hits recorded
- 0 / 75engines flagged
- 3,691sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
4 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
0 of 75 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
YARAify matched 3 researcher rules to this file.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: qbittorrent_5.2.3_x64_setup.exe — ff508e2f912d59c9eabaf03633ebacfd45c2049f38dcac027b8a7d7ad867ab2f
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\qbittorrent_5.2.3_x64_setup.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Program Files\qBittorrent\qbittorrent.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: nsqE705.tmp — C:\Users\<USER>\AppData\Local\Temp\nsqE705.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: UAC.dll — C:\Users\<USER>\AppData\Local\Temp\nslE735.tmp\UAC.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 162.159.36.2 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
One or more independent reference databases matched 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.
- CP_Script_Inject_Detector
- Detect_NSIS_Nullsoft_Installer
- NSIS
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\svchost.exe -k NetworkService -pSandbox 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.
Evidence162.159.36.2
0 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
- qbittorrent_5.2.3_x64_setup.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 41.1 MB
- Last analyzed
- Aug 27, 2026, 5:51 AM UTC
ff508e2f912d59c9eabaf03633ebacfd45c2049f38dcac027b8a7d7ad867ab2fSafety & 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 install 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. Download a fresh installer 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 qbittorrent_5.2.3_x64_setup.exe safe, or is it malware?
What is qbittorrent_5.2.3_x64_setup.exe?
How many antivirus engines detected qbittorrent_5.2.3_x64_setup.exe?
I already downloaded and installed qbittorrent_5.2.3_x64_setup.exe — what should I do?
How do I remove qbittorrent_5.2.3_x64_setup.exe?
What is the SHA-256 hash of qbittorrent_5.2.3_x64_setup.exe?
How up to date is this analysis of qbittorrent_5.2.3_x64_setup.exe?
Community
Member reviews and reports for this exact file hash.