Is TikTok Downloader Setup(x64).exe safe?
Only Bkav flagged this widely submitted installer, but unsigned provenance and sandbox indicators involving process injection and LSASS warrant verification before execution.
The antivirus result strongly resembles a false positive: only 1 of 74 engines flagged the file, and no tier-1 engine agreed. However, the unsigned executable produced process-injection, defense-impairment, and LSASS-related indicators, while its IP contacts received no complete reputation check, so execution should wait for source and hash verification.
216e8c169b6ce9658f…f47c5516a1cfd7Recommended 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.
The antivirus result strongly resembles a false positive: only 1 of 74 engines flagged the file, and no tier-1 engine agreed. However, the unsigned executable produced process-injection, defense-impairment, and LSASS-related indicators, while its IP contacts received no complete reputation check, so execution should wait for source and hash verification.
Bkav was the only detector among 74 engines, and all 16 tier-1 engines reported no detection, making the generic label weak in isolation. The filename, approximate size, version artifacts, and first-seen date align closely with the official Jettcodey 1.3.9 release. Nevertheless, this executable is unsigned, so that alignment does not authenticate its origin. One completed sandbox recorded T1055, T1485, T1562.001, and LSASS-related activity, although it did not issue a malicious sandbox verdict. No child was identified as malware and external intelligence supplied no corroborating hit, but the children remain unclassified and no complete reputation result exists for the contacted IP addresses.
What We Detected
Bkav alone flagged the sample as W32.Malware.BA071D79; the other 73 of 74 engines did not flag it, including all 16 tier-1 engines. The sample has also circulated for 466 days across 235 sources and 243 submissions. Its name, approximate 42 MB size, version artifacts, and first-seen date match the official Jettcodey TikTok Downloader 1.3.9 release, but the executable is unsigned and therefore cannot be cryptographically linked to that publisher.
Threat Behavior
One completed sandbox recorded MITRE techniques T1055, T1485, and T1562.001, along with a heuristic indicating activity involving LSASS. Those signals can represent process injection, data destruction, defense impairment, or credential-access behavior, although the sandbox itself did not produce a malicious verdict. Eleven IP addresses were observed, but contactedHosts is unavailable, so no complete reputation assessment exists for those contacts. Ten dropped files were inspected without a malicious finding, but all ten remain unclassified rather than confirmed benign.
What To Do Now
Keep endpoint protection enabled and obtain the installer only from the official Jettcodey release page. Compare its SHA-256 hash with a hash published through an authenticated release channel; if that cannot be done, avoid running it on a production system. Users who already executed it should run a full endpoint scan and review unusual processes or account activity.
Where this verdict could be wrong4 caveats
- The low-trust-only antivirus pattern normally suggests a false positive, with all 16 tier-1 engines reporting no detection.
- The official Jettcodey 1.3.9 release matches the executable name, approximate 42 MB size, and 2025-06-07 release date, although the unsigned file cannot be cryptographically tied to that release.
- No sandbox produced a malicious verdict, no inspected child was marked malicious, and YARAify, CIRCL, and MalwareBazaar supplied no corroborating hit.
- Runtime mappings include process injection, defense impairment, and LSASS-related activity, which are difficult to dismiss without a complete host check or publisher authentication.
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/74 engines flagged the sample
- engines.tier1Malicious=0, with all 16 tier-1 engines reporting no detection
- prevalence shows 235 sources and 243 submissions over 466 days
- behaviour.hasMaliciousSandboxVerdict=false
- externalIntel.yaraify.ruleCount=0 and externalIntel.malwareBazaar.hit=false
- Unsigned Win32 executable with no authenticated publisher
- Sandbox mapped activity to T1055 process injection
- Sandbox mapped activity to T1562.001 defense impairment
- LSASS-related activity triggered MalwareTips.Synth.CredentialDumper
- Observed IP contacts lack a complete contactedHosts reputation result
- Ten dropped children remain unknown rather than confirmed benign
Keep protection enabled and use only the installer obtained directly from the official Jettcodey release page after verifying its SHA-256. Otherwise, avoid execution or test it only in an isolated environment.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial11 runtime contacts were observed without a completed reputation cross-check.
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
- 23MITRE ATT&CK techniques
- 15spawned processes
- 11network contacts
- 32filesystem & 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: Attempted to impair or bypass security controls.
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
TikTok Downloader Setup(x64).exe
216e8c169b6ce9658f68cbf037920f8d16442f25a5b2a32b0df47c5516a1cfd7
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\TikTok.Downloader.Setup.x64.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\services.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
holder0.aiph
C:\Users\<USER>\AppData\Roaming\Jettcodey\TikTok Downloader 1.3.9\install\holder0.aiph
04Isolated runtime analysis - Written fileObserved
TikTok Downloader Setup(x64).msi
C:\Users\<USER>\AppData\Roaming\Jettcodey\TikTok Downloader 1.3.9\install\TikTok Downloader Setup(x64).msi
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
a83f:8110:4183:b4ff:4183:b4ff:4183:b4ff
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
192.168.0.56
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.
- a83f:8110:4183:b4ff:4183:b4ff:4183:b4ff
- 192.168.0.56
- 20.99.133.109
- 23.55.140.42
- 20.69.140.28
- 23.196.145.221
- 23.46.228.49
- 23.53.122.210
- 184.27.218.92
- 23.46.228.41
- C:\Users\<USER>\AppData\Roaming\Jettcodey\TikTok Downloader 1.3.9\install\holder0.aiph
- C:\Users\<USER>\AppData\Roaming\Jettcodey\TikTok Downloader 1.3.9\install\TikTok Downloader Setup(x64).msi
- C:\Users\<USER>\AppData\Local\Temp\shi33BD.tmp
- C:\Users\<USER>\AppData\Local\Temp\AI_EXTUI_BIN_3356\aboutbtndark
- C:\Users\<USER>\AppData\Local\Temp\AI_EXTUI_BIN_3356\infoIconMsi
- C:\Windows\SysWOW64\MsiWerCrashmetadata-41
- %USERPROFILE%\AppData\Local\Temp\shi87.tmp
- %USERPROFILE%\AppData\Local\Temp\MSI24E.tmp
- %USERPROFILE%\AppData\Local\Temp\MSI368.tmp
- %USERPROFILE%\AppData\Local\Temp\MSI54D.tmp
- Local\SessionImmersiveColorMutex
- Global\OneSettingQueryMutex+compat+encapsulation
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 80c5e769470bb98c5b1e…ceb76fNever scannednever seen before
- 8d3e94c47af3da706a9f…e472b8Never scannednever seen before
- 047e2df9ccf0ce298508…9d064bNever scannednever seen before
- 34fe948e2b005a424f4e…70d95aNever scannednever seen before
- d23ab5db755cbdeaef24…8f365fNever scannednever seen before
- 9d7243c688264329a8cb…ee1335Never scannednever seen before
- 75fea1443a0af7375627…f8f1cdNever scannednever seen before
- 205a20e410235b12b18c…3260baNever scannednever seen before
- 27f13c4829994b214bb1…e02b5fNever scannednever seen before
- ed127a86f01d767643af…7ee7faNever 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.
- 3rule hits recorded
- 1 / 74engines flagged
- 235sources 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
1 of 74 antivirus engines flagged the file, including Bkav.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has a long, established submission history across 235 sources.
ProvenanceDerivedSourceSubmission historyObserved at - 04
Scanned file: TikTok Downloader Setup(x64).exe — 216e8c169b6ce9658f68cbf037920f8d16442f25a5b2a32b0df47c5516a1cfd7
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\TikTok.Downloader.Setup.x64.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\services.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: holder0.aiph — C:\Users\<USER>\AppData\Roaming\Jettcodey\TikTok Downloader 1.3.9\install\holder0.aiph
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: TikTok Downloader Setup(x64).msi — C:\Users\<USER>\AppData\Roaming\Jettcodey\TikTok Downloader 1.3.9\install\TikTok Downloader Setup(x64).msi
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: a83f:8110:4183:b4ff:4183:b4ff:4183:b4ff — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 192.168.0.56 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
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\svchost.exe -k LocalSystemNetworkRestricted -p -s WdiSystemHostSandbox 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.
Evidencea83f:8110:4183:b4ff:4183:b4ff:4183:b4ff · 20.99.133.109 · 23.55.140.42
1 of 74 engines flagged this file
View all 74 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
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Fingerprint and provenance
- File name
- TikTok Downloader Setup(x64).exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 42.0 MB
- Last analyzed
- Sep 16, 2026, 4:07 PM UTC
216e8c169b6ce9658f68cbf037920f8d16442f25a5b2a32b0df47c5516a1cfd7Safety & 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 TikTok Downloader Setup(x64).exe safe, or is it malware?
What is TikTok Downloader Setup(x64).exe?
How many antivirus engines detected TikTok Downloader Setup(x64).exe?
What should I do if I already ran TikTok Downloader Setup(x64).exe?
How do I remove TikTok Downloader Setup(x64).exe?
What is the SHA-256 hash of TikTok Downloader Setup(x64).exe?
How up to date is this analysis of TikTok Downloader Setup(x64).exe?
Community
Member reviews and reports for this exact file hash.