File scan report
Verdict Suspicious
Is JDownloader2 Setup_ windows- x86_ v11_ 0_ 29. exe safe? Treat it as suspicious.
9 of the 69 antivirus engines that checked it flag this Windows program, but nothing confirms it is harmful.
Why Suspicious? 9 antivirus engines flag it; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
If it came from a link, an attachment or a stranger, delete it.
What to do now4 steps
Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.
What to do
Don't run it unless you're sure where it came from.
Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.
If you can't confirm where it came from, delete it. If you need the program, download it again from the publisher's own website.
If you already ran it
Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.
Not sure what to do?
Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
9 of 69 flagged
- Flagged 9
- No detection 60
- No result 6
- Code signing Unsigned
- Test run Completed
- First seen 5mo ago
Chapter 02
Why we think so
4 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
It unpacks standard install4j/Java files with no malicious files it created or contacts. Likely a false positive on a legitimate downloader, but verify from official sources.
The file matches a known legitimate installer for JDownloader, which uses install4j and extracts Java runtime components. Major detections are generic (FileRepMalware) common for recent files, outweighed by 14 clean major scans. Unsigned status and new age contribute to caution without strong malicious consensus.
What We Detected
9/69 engines flagged malicious, led by Avast/AVG FileRepMalware and Ikarus Kryptik; majority undetected including Kaspersky, ESET, BitDefender.
What To Do Now
Download only from official JDownloader site (jdownloader.org). If needed, run in sandbox or scan with updated AV.
Where this verdict could be wrong2 caveats
- 3 major antivirus engines (Avast, AVG, Ikarus) flag malicious with 'FileRepMalware'/'Kryptik' — could indicate real threat despite majority clean.
- Unsigned with reputation=-1 and age=2 days — lacks publisher trust signals.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 14 major antivirus engines clean (ESET, Kaspersky, etc.)
- Benign installer drops (install4j, JRE)
- No malicious sandbox verdict
- Filename matches legit JDownloader installer
- Unsigned executable
- Recent first submission (2 days)
- 3 malicious detections from major antivirus engines
- Generic 'FileRepMalware' labels
6 sources checked · 5 complete · 1 not needed or not applicable. 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- 15sandbox rule tags
- 3spawned processes
- 0network contacts
- 21filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
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: Checked whether it was running on a test computer.
Note: Read the user name of the test computer.
Note: Read basic details of the test computer, such as its Windows version.
Note: Looked through folders on the test computer (most installers do this).
Note: Loaded extra code modules while running.
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.
Not confirmed: A sandbox rule tagged this run as contacting a server, but no contacted host was recorded.
Not confirmed: A sandbox rule tagged this run as downloading a file, but no download was recorded.
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.
Recorded behavior
What happened in the test
Grouped by step. The order is not a timeline.
- 1
Input file
The submitted object
- Evidence 1 of 5: FileSeen in the test run
JDownloader2Setup_windows-x86_v11_0_29.exe
de8b2bdfc61d63585329b8cfca2a012476b46387435410b995aeae5b502bd95e
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 5: ProcessSeen in the test run
JDownloader2Setup_windows-x86_v11_0_29.exe
"C:\Users\<USER>\Desktop\JDownloader2Setup_windows-x86_v11_0_29.exe"
Test run - Evidence 3 of 5: ProcessSeen in the test run
tmp11FA.exe
"C:\Users\<USER>\AppData\Local\Temp\tmp11FA.exe"
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 5: Written fileSeen in the test run
tmp11FA.exe
C:\Users\<USER>\AppData\Local\Temp\tmp11FA.exe
Test run - Evidence 5 of 5: Written fileSeen in the test run
i4j_nlog_1.log
C:\Users\<USER>\AppData\Local\install4j\t\i4j_nlog_1.log
Test run - +1 more recorded observation
5 facts from the test run. See the full activity list.
Includes 15 mapped techniques, every process, file, registry and network entry and 10 dropped files.
Show the technical evidenceChapter 04
Technical details
9 of the 69 antivirus engines that checked it flag it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 9
- Avast (major engine)FileRepMalware [Misc]
- AVG (major engine)FileRepMalware [Misc]
- Ikarus (major engine)Trojan.Win64.Krypt
- BkavW32.Malware.3A071CB4
- DeepInstinctMALICIOUS
- GoogleDetected
- McAfeeDti!DE8B2BDFC61D
- RisingTrojan.Kryptik@AI.80 (RDML:235PalrdQqZJ5gQtK0qWtw)
File fingerprint
- Last analyzed
- May 8, 2026, 5:16 PM UTC
- SHA-256
de8b2bdfc61d63585329b8cfca2a012476b46387435410b995aeae5b502bd95e- SHA-1
c5997e6a28a46041180780eb52842b668a65e4e2- MD5
d3b398a757b424f91e645985ade00516
About this file
JDownloader2Setup_windows-x86_v11_0_29.exe is a Win32 EXE file of 87.2 MB.
- Type and size
- Win32 EXE · 87.2 MB
- Signer
- UnsignedNo code signature.
- First seen
- May 6, 2026On VirusTotal.
- Submitted by
- 9 distinct sourcesRarely seen: few people have submitted this exact file.
- Packer
- None detected
- Entropy
- 8.00 of 8
First scanned
Includes every engine result (75), 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 JDownloader2Setup_windows-x86_v11_0_29.exe safe, or is it malware?
What is JDownloader2Setup_windows-x86_v11_0_29.exe?
How many antivirus engines detected JDownloader2Setup_windows-x86_v11_0_29.exe?
I already downloaded and ran JDownloader2Setup_windows-x86_v11_0_29.exe — what should I do?
What is the SHA-256 hash of JDownloader2Setup_windows-x86_v11_0_29.exe?
How up to date is this analysis of JDownloader2Setup_windows-x86_v11_0_29.exe?
Community
Member reviews and reports for this exact file hash.