Is DDNet-20.0-win64.zip safe?
Only 2 of 74 engines detected the archive, but a tier-1 Trojan label and concerning sandbox technique mappings warrant caution.
The archive has limited antivirus detection—2 of 74 engines—with no agreed malware family or malicious sandbox verdict. However, one tier-1 engine reported a generic Trojan and runtime analysis mapped activity to process injection and defense impairment, so execution should be avoided until its source and contents are independently verified.
bec7dc8441fbf42684…d4b2ceec967d39Recommended next actions
Before opening or extracting
Do not open or extract it until the source can be verified independently.
If you already opened or extracted it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the original trusted source and verify its exact hash when possible.
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 archive has limited antivirus detection—2 of 74 engines—with no agreed malware family or malicious sandbox verdict. However, one tier-1 engine reported a generic Trojan and runtime analysis mapped activity to process injection and defense impairment, so execution should be avoided until its source and contents are independently verified.
Two of 74 engines flagged the archive, including Ikarus with a generic Agent Trojan label, while the other 16 reporting tier-1 engines did not detect it. No engine family consensus, malicious sandbox verdict, malicious child, or external-intelligence match corroborates that label. The completed sandbox run nevertheless mapped activity to T1055 process injection and T1562.001 defense impairment, alongside three other offensive techniques. The rundll32 loading of bundled DLLs may reflect sandbox probing or application behavior, but it remains a meaningful concern. Reputation checking covered the four observed URLs but not demonstrably all six contacted IP addresses, so the network evidence is incomplete. Overall, the evidence is mixed and does not establish a specific malware family.
What We Detected
Two of 74 antivirus engines flagged the archive. Ikarus reported Trojan.Win64.Agent, while Google returned a generic detection; there was no high-trust family consensus, and 16 other reporting tier-1 engines did not detect it. No CIRCL, MalwareBazaar, or YARAify corroboration was present.
Threat Behavior
One completed sandbox run mapped activity to T1055, T1485, T1548, T1560, and T1562.001. In particular, rundll32 attempted to load several DLLs from the extracted archive, which contributed to the process-injection heuristic. The sandbox did not issue a malicious verdict, recorded no persistence indicators, and found no confirmed malicious child among 10 inspected files, although every child retained an unknown individual verdict. Four observed URLs were reputation-checked without a known harmful match, but six IP contacts were also recorded and complete reputation coverage across every contact was not established.
What To Do Now
Do not run the archive unless it came directly from the project's official release channel and its SHA-256 hash can be verified against an official checksum. Keep endpoint protection enabled, and if verification is unavailable, quarantine or delete the file and obtain a fresh copy from the official source.
Where this verdict could be wrong4 caveats
- Ikarus is a tier-1 detector and labeled the sample Trojan.Win64.Agent, so the two detections cannot be dismissed as low-trust noise.
- The sandbox mapped activity to T1055 and T1562.001, both concerning even though no malicious sandbox verdict was issued.
- Six IP addresses were observed, but contactedHosts.inspected=4 does not establish complete reputation coverage for every contact.
- All 10 inspected children have unknown individual verdicts; hasMaliciousChild=false therefore provides limited reassurance.
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 2/74 engines detected the archive
- engines.tier1FamilyConsensus.strong=false
- behaviour.hasMaliciousSandboxVerdict=false
- droppedChildren.hasMaliciousChild=false
- externalIntel.yaraify.ruleCount=0 and externalIntel.malwareBazaar.hit=false
- Ikarus tier-1 detection: Trojan.Win64.Agent
- Google generic malicious detection
- Sandbox mapping to T1055 process injection
- Sandbox mapping to T1562.001 defense impairment
- Incomplete reputation coverage for six observed IP contacts
- All 10 extracted child verdicts remain unknown
Verify SHA-256 bec7dc8441fbf4268481182a6adcfc39527296b875396b844ed4b2ceec967d39 against the project's official release channel before use. Keep endpoint protection enabled and avoid execution if the hash or source cannot be confirmed.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete2 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial4 of 10 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete2 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
- 19MITRE ATT&CK techniques
- 15spawned processes
- 10network contacts
- 40filesystem & 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: Removed execution artefacts or logs, which can conceal activity.
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.
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
DDNet-20.0-win64.zip
bec7dc8441fbf4268481182a6adcfc39527296b875396b844ed4b2ceec967d39
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\DDNet-20.0-win64/libcurl.dll",#1
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\DDNet-20.0-win64/zlib1.dll",#1
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
SvcRestartTask
C:\Windows\System32\Tasks\Microsoft\Windows\SoftwareProtectionPlatform\SvcRestartTask
04Isolated runtime analysis - Written fileObserved
Temp
C:\ProgramData\Microsoft\Windows\WER\Temp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
104.18.10.44
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
69.63.215.182
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.
- 104.18.10.44
- 69.63.215.182
- 23.205.110.143
- 104.18.21.213
- 46.174.54.240
- 74.125.250.129
- http://x2.c.lencr.org/
- http://ye.c.lencr.org/
- http://ye2.c.lencr.org/17.crl
- http://ye1.c.lencr.org/125.crl
- C:\Windows\System32\Tasks\Microsoft\Windows\SoftwareProtectionPlatform\SvcRestartTask
- C:\ProgramData\Microsoft\Windows\WER\Temp
- C:\ProgramData\Microsoft\Windows\WER\Temp\a3b95bd6-48a5-4968-9df3-b47a2d99a7f6
- C:\ProgramData\Microsoft\Windows\WER\ReportQueue
- C:\ProgramData\Microsoft\Windows\WER\Temp\ced3392d-7b7d-4005-bec4-860ef42ed6c2
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER9B2C.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERAEE4.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERD26B.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER9B2C.tmp.dmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERAEE4.tmp.WERInternalMetadata.xml
- Local\WERReportingForProcess4224
- Global\67dc45b4-5332-43cc-9370-7d3ffe77e57a
- Local\WERReportingForProcess5768
- Global\31f116ab-5a92-4bf4-af1d-492ead6080e4
- Local\SessionImmersiveColorMutex
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 17ff7b99b63507fccd7f…1a1426Never scannednever seen before
- ed133c0a01b9f5f314c4…14efe9Never scannednever seen before
- a952e36df71b193af841…dbb437Never scannednever seen before
- bd60f3fc1978e8fdad65…5f447bNever scannednever seen before
- 5622a8117f5c0348c16b…621e8aNever scannednever seen before
- f91f5bb90d654ea6d635…c43caaNever scannednever seen before
- f83bbe64c6c9bcef7acb…6e38a6Never scannednever seen before
- 004535c74020fc75c207…4cf042Never scannednever seen before
- dda8a00bea3c4064cba8…ca76baNever scannednever seen before
- 9f67f4143eeff6fa26e0…721d9fNever 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.
- 2rule hits recorded
- 2 / 74engines flagged
- 28sources 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
2 of 74 antivirus engines flagged the file, including Google and Ikarus.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 31 times from 28 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: DDNet-20.0-win64.zip — bec7dc8441fbf4268481182a6adcfc39527296b875396b844ed4b2ceec967d39
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\DDNet-20.0-win64/libcurl.dll",#1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\DDNet-20.0-win64/zlib1.dll",#1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: SvcRestartTask — C:\Windows\System32\Tasks\Microsoft\Windows\SoftwareProtectionPlatform\SvcRestartTask
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: Temp — C:\ProgramData\Microsoft\Windows\WER\Temp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 104.18.10.44 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 69.63.215.182 — 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.
Evidence"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\DDNet-20.0-win64/libcurl.dll",#1The 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.
Evidence104.18.10.44 · 69.63.215.182 · 23.205.110.143
2 of 74 engines flagged this file
View all 74 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- DDNet-20.0-win64.zip
- Format
- ZIP
- Code signing
- Not applicable to this file type
- Size
- 62.7 MB
- Last analyzed
- Sep 21, 2026, 1:12 PM UTC
bec7dc8441fbf4268481182a6adcfc39527296b875396b844ed4b2ceec967d39Safety & 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 open or extract 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 archive and use a fresh copy from a trusted source. Get a fresh copy from the original trusted source and verify its exact hash when possible.
- 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 DDNet-20.0-win64.zip safe, or is it malware?
What is DDNet-20.0-win64.zip?
How many antivirus engines detected DDNet-20.0-win64.zip?
I already downloaded and opened or extracted DDNet-20.0-win64.zip — what should I do?
How do I remove DDNet-20.0-win64.zip?
What is the SHA-256 hash of DDNet-20.0-win64.zip?
How up to date is this analysis of DDNet-20.0-win64.zip?
Community
Member reviews and reports for this exact file hash.