Is ModManager (x64) 1.0.0.59.zip safe?
No antivirus engine detected the long-circulating archive, although one sandbox recorded process-loading and direct-IP activity that lacks a complete host-reputation check.
All 75 antivirus engines were free of detections, including 17 tier-1 engines, and the archive has circulated widely since 2015. One sandbox recorded potentially offensive techniques and 11 direct-IP contacts, but produced no malicious runtime verdict; those IPs were not fully reputation-checked.
39550fdf9b9647dcff…7da09552df003fRecommended next actions
Before opening or extracting
Open or extract it only when its sender or download source has been independently verified.
If you already opened or extracted it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
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.
All 75 antivirus engines were free of detections, including 17 tier-1 engines, and the archive has circulated widely since 2015. One sandbox recorded potentially offensive techniques and 11 direct-IP contacts, but produced no malicious runtime verdict; those IPs were not fully reputation-checked.
The archive received no malicious or suspicious detections from 75 antivirus engines, including 17 tier-1 engines. It has been observed since 2015 across 256 sources and 480 submissions, making an undiscovered commodity threat less likely. One completed sandbox run mapped activity to T1055 and three other offensive techniques, but it did not issue a malicious sandbox verdict. Ten extracted children were inspected without a confirmed malicious child, although their individual verdicts remain unresolved. The 11 contacted IP addresses lack a complete host-reputation assessment, so the no complete contacted-host reputation result was available. Overall, the extensive detection history outweighs the uncorroborated behavioural heuristics.
What We Detected
No malicious or suspicious detection was reported among 75 antivirus engines. This includes 17 tier-1 engines, such as Avast, BitDefender, ESET-NOD32, Kaspersky, and Fortinet. The archive has also circulated since 2015, with 256 sources and 480 submissions, without accumulating a malware family label.
Threat Behavior
One sandbox run mapped activity to T1005, T1055, T1543.002, and T1562.001. It also observed rundll32 loading a temporary DLL and connections to 11 IP addresses, but issued no malicious sandbox verdict. Host reputation was not completely checked for those IP addresses. Ten extracted children were inspected without a confirmed malicious child, though their individual classifications remain unknown.
What To Do Now
Obtain the archive from its original trusted distribution channel and keep endpoint protection enabled while extracting or running it. If the source is uncertain, verify the SHA-256 hash and consider monitoring outbound connections during first use.
Where this verdict could be wrong3 caveats
- The MalwareTips.Synth.ProcessInjection heuristic mapped rundll32 loading zlib.net.dll to T1055, which warrants caution despite the lack of engine detections.
- The MalwareTips.Synth.DirectIpC2 heuristic recorded 11 direct-IP contacts, while contactedHosts=null means their reputations were not completely checked.
- All 10 extracted children have unknown verdicts, so droppedChildren.hasMaliciousChild=false does not establish that every archive component is benign.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0/75 antivirus engines reported a malicious or suspicious result.
- All 17 reporting tier-1 engines returned no detection.
- Observed since 2015 across 256 sources and 480 submissions.
- No malicious sandbox verdict was issued.
- No malicious child or external-intelligence hit was confirmed.
- Sandbox evidence mapped DLL loading through rundll32 to T1055.
- Four offensive MITRE techniques were recorded in one sandbox run.
- Eleven direct-IP contacts were observed without a complete host-reputation result.
- The 10 extracted children have unresolved individual verdicts.
Use a copy obtained from the original trusted source, verify its SHA-256 hash, and keep endpoint protection enabled. Exercise extra caution if the program makes unexpected outbound connections.
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
Partial11 runtime contacts were observed without a completed reputation cross-check.
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
- 18MITRE ATT&CK techniques
- 13spawned processes
- 11network contacts
- 40filesystem & mutex artifacts
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
ModManager (x64) 1.0.0.59.zip
39550fdf9b9647dcfffc049551908673ef01e18cd364486db47da09552df003f
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\zlib.net.dll",#1
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\DAIModManager.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Caches
C:\Users\user\AppData\Local\Microsoft\Windows\Caches
04Isolated runtime analysis - Written fileObserved
Explorer
C:\Users\user\AppData\Local\Microsoft\Windows\Explorer
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
72.21.81.240
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
40.126.62.130
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.
- 72.21.81.240
- 40.126.62.130
- 104.107.106.121
- 52.142.223.178
- 40.68.123.157
- 13.64.180.106
- 20.163.45.184
- 23.75.209.56
- 52.183.220.149
- 20.72.205.209
- C:\Users\user\AppData\Local\Microsoft\Windows\Caches
- C:\Users\user\AppData\Local\Microsoft\Windows\Explorer
- C:\Users\user\AppData\Local\Temp\hwvkn1l0.nvd
- C:\Users\user\AppData\Local\Temp\hwvkn1l0.nvd\DAIModManager.exe
- C:\Users\user\AppData\Local\Temp\hwvkn1l0.nvd\DAIModManager.pdb
- /tmp/tmp.O97UuZdIbq
- /tmp/tmp.Trf6jCFwuy
- /tmp/tmp.l9VxJik2iO
- /var/lib/logrotate/status.tmp
- /var/log/apport.log.1
- Local\SM0:3060:168:WilStaging_02
- Local\SM0:72:304:WilStaging_02
- Local\__DDrawExclMode__
- Local\__DDrawCheckExclMode__
- Local\SM0:72:120:WilError_03
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 9425a94647b42358f53c…f28684Never scannednever seen before
- 50a7d0bccdf7ef5a79c4…b8b92bNever scannednever seen before
- 027b7c46a3ca0625b51b…3041c3Never scannednever seen before
- 4d9e6128c4ab80e391b0…02fe34Never scannednever seen before
- 4167b599f36af0781b81…4b516aNever scannednever seen before
- 82f28a88ecd35659cf9b…c9b38eNever scannednever seen before
- 2b5473c70e0dd22f6f0c…1cb73dNever scannednever seen before
- 300d468f8909489002e6…add512Never scannednever seen before
- 7311547a87c75f92566f…424ac9Never scannednever seen before
- 62e058bef6819056d9d3…f10746Never 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
- 0 / 75engines flagged
- 256sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 75 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 256 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 04
Scanned file: ModManager (x64) 1.0.0.59.zip — 39550fdf9b9647dcfffc049551908673ef01e18cd364486db47da09552df003f
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\zlib.net.dll",#1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\<USER>\AppData\Local\Temp\DAIModManager.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Caches — C:\Users\user\AppData\Local\Microsoft\Windows\Caches
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: Explorer — C:\Users\user\AppData\Local\Microsoft\Windows\Explorer
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 72.21.81.240 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 40.126.62.130 — 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\zlib.net.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.
Evidence72.21.81.240 · 40.126.62.130 · 104.107.106.121
0 of 75 engines flagged this file
View all 75 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
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
- ModManager (x64) 1.0.0.59.zip
- Format
- ZIP
- Code signing
- Not applicable to this file type
- Size
- 138.9 KB
- Last analyzed
- Sep 9, 2026, 6:43 PM UTC
39550fdf9b9647dcfffc049551908673ef01e18cd364486db47da09552df003fSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Open or extract it only when its sender or download source has been independently verified.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is ModManager (x64) 1.0.0.59.zip safe?
What is ModManager (x64) 1.0.0.59.zip?
How many antivirus engines detected ModManager (x64) 1.0.0.59.zip?
What is the SHA-256 hash of ModManager (x64) 1.0.0.59.zip?
Is it safe to open or extract ModManager (x64) 1.0.0.59.zip?
How up to date is this analysis of ModManager (x64) 1.0.0.59.zip?
Community
Member reviews and reports for this exact file hash.