Is Kemono.Downloader.exe safe?
Four of 75 engines flagged this unsigned executable, but limited runtime observation and external research produced no corroborating malicious behavior or infrastructure.
Microsoft and Gridinsoft applied Wacatac labels, while two lower-trust engines issued generic detections. However, only one tier-1 engine flagged it, one completed runtime observation found no malware-exclusive behavior, and external research returned no matching threat intelligence, leaving materially mixed evidence.
720dc2f025d6afa428…0094599ce3d99eRecommended 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.
Microsoft and Gridinsoft applied Wacatac labels, while two lower-trust engines issued generic detections. However, only one tier-1 engine flagged it, one completed runtime observation found no malware-exclusive behavior, and external research returned no matching threat intelligence, leaving materially mixed evidence.
Four of 75 engines detected the executable, with Microsoft providing the sole tier-1 detection and Gridinsoft independently using a similar Wacatac label. There is no strong tier-1 family consensus, and the remaining detections are generic results from lower-trust engines. The file is unsigned and lacks publisher history, so its origin cannot be authenticated. One completed runtime observation recorded only ambient techniques, no malicious sandbox conclusion, no persistence, and no dropped files. The observed hosts were fully checked against the available cache without a threat hit, while YARAify, CIRCL, and MalwareBazaar supplied no corroboration. These opposing signals warrant caution rather than a definitive malware-family attribution.
What We Detected
Four of 75 antivirus engines flagged the executable. Microsoft reported Wacatac through a machine-learning label, Gridinsoft used a similar Wacatac name, and APEX and Bkav supplied generic detections. Only Microsoft represents a tier-1 malicious vote, and there is no strong tier-1 family consensus.
Threat Behavior
One completed runtime observation recorded nine benign-common techniques, including T1027, T1059, and T1082, but no malware-exclusive techniques. It found no persistence indicators, written files, dropped payloads, or malicious sandbox conclusion. The cache check covered the observed domain and IP and returned no malicious or suspicious reputation hits; external intelligence and YARA rules also provided no corroboration.
What To Do Now
Because the executable is unsigned and has several detections, avoid running it on an important system until its source and checksum can be verified through the project's official release channel. Keep endpoint protection enabled, and use an isolated environment if further testing is necessary.
Where this verdict could be wrong3 caveats
- Microsoft and Gridinsoft both used Wacatac labels, although Microsoft is the only tier-1 malicious vote and the label is generic or machine-learning based.
- The executable is unsigned, which removes publisher assurance even though unsigned software is not inherently harmful.
- T1027 and T1059 appeared during execution, but behaviour.offensiveCount=0 classifies all nine observed techniques as ambient rather than malware-exclusive.
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/17 tier-1 engines flagged the sample, with 12 tier-1 engines reporting it undetected.
- One completed runtime observation produced no malicious conclusion or malware-exclusive technique.
- No persistence, dropped files, or malicious child payload was observed.
- The complete observed-host cache check found no malicious or suspicious reputation hit.
- YARAify, CIRCL, and MalwareBazaar returned no match.
- 4/75 antivirus engines reported malicious results.
- Microsoft supplied one tier-1 Wacatac detection.
- The Win32 executable is unsigned and has no signer history.
- Gridinsoft independently used a Wacatac label.
- The downloader-style filename implies network-facing functionality, though filename alone is not proof.
Do not run the file unless its hash can be verified against an official project release. Keep endpoint protection enabled and quarantine or isolate it if provenance cannot be established.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete4 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 of 2 contacted hosts were cross-checked; coverage is incomplete.
YARA
CompleteRule evaluation completed with no recorded matches.
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
- 9MITRE ATT&CK techniques
- 2spawned processes
- 2network contacts
- 0filesystem & mutex artifacts
What this file does
Observed actions and their security significance
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.
Moderate concern: Checked the environment for virtualisation or analysis tools.
Note: Listed running processes; both legitimate software and malware may do this.
Note: Collects details about your system.
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
Kemono.Downloader.exe
720dc2f025d6afa4289b808d3541c6fe8f27f80ded92d8193a0094599ce3d99e
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\Kemono.Downloader.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\user\Desktop\Kemono.Downloader.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
a1672.dscr.akamai.net
Contact observed during runtime.
04Isolated runtime analysis - Contacted hostObserved
162.159.36.2
Contact observed during runtime.
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
5 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.
- a1672.dscr.akamai.net
- 162.159.36.2
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 0rule hits recorded
- 4 / 75engines flagged
- 85sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
4 of 75 antivirus engines flagged the file, including APEX and Bkav.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 93 times from 85 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: Kemono.Downloader.exe — 720dc2f025d6afa4289b808d3541c6fe8f27f80ded92d8193a0094599ce3d99e
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Users\<USER>\Desktop\Kemono.Downloader.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — "C:\Users\user\Desktop\Kemono.Downloader.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Contacted host: a1672.dscr.akamai.net — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
Contacted host: 162.159.36.2 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: generic-trojan
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
YARA rules
No matchesThe rule pass completed without a saved public match.
4 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
- Kemono.Downloader.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 14.6 MB
- Last analyzed
- Oct 3, 2026, 12:12 AM UTC
720dc2f025d6afa4289b808d3541c6fe8f27f80ded92d8193a0094599ce3d99eSafety & 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 Kemono.Downloader.exe safe, or is it malware?
What is Kemono.Downloader.exe?
How many antivirus engines detected Kemono.Downloader.exe?
What should I do if I already ran Kemono.Downloader.exe?
How do I remove Kemono.Downloader.exe?
What kind of malware is Kemono.Downloader.exe?
What is the SHA-256 hash of Kemono.Downloader.exe?
How up to date is this analysis of Kemono.Downloader.exe?
Community
Member reviews and reports for this exact file hash.