Is DrCoconut Dupe Mod 1.21.11 V4.jar.zip safe?
None of 74 engines detected the JAR, and one completed sandbox run produced no malicious verdict or confirmed malicious child.
The strongest evidence is favorable: 0 of 74 engines detected the file, including all 17 reporting tier-1 engines. One sandbox run produced no malicious verdict, but the service-related T1543.002 observation and unresolved child-file classifications justify ordinary caution with this recently observed mod.
98fdb55025b8fecd67…b3a3e13896ec09Recommended 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.
The strongest evidence is favorable: 0 of 74 engines detected the file, including all 17 reporting tier-1 engines. One sandbox run produced no malicious verdict, but the service-related T1543.002 observation and unresolved child-file classifications justify ordinary caution with this recently observed mod.
Static scanning produced no malicious or suspicious detections among 74 engines, with 17 tier-1 engines reporting no detection. One completed sandbox observation did not issue a malicious verdict, and no persistence indicator or network contact was recorded. T1543.002 appeared in the behavioral mapping, but the associated commands concern CUPS service handling and log rotation, making sandbox-environment activity a plausible explanation. Five written files were inspected without a confirmed malicious child, although their individual classifications remain unresolved. Research feeds supplied no malware family, YARA rule, or known-malicious reference for this hash. The evidence therefore supports benign handling while retaining normal caution for a recently observed third-party game mod.
What We Detected
None of 74 antivirus engines flagged this JAR, and all 17 reporting tier-1 engines returned no detection. No malware family was identified, while the available researcher feeds returned no matching YARA rules or known-malicious references.
Threat Behavior
One completed sandbox run produced no malicious verdict and recorded no contacted domains, IPs, or URLs. It mapped T1543.002, but the captured commands involved restarting the CUPS service and rotating system logs; no persistence indicator was recorded. Five written files were inspected without a confirmed malicious child, although each child remains individually unclassified. No complete contacted-host reputation result is available because that cross-check was not saved.
What To Do Now
Obtain the mod from its official project or creator page and verify the SHA-256 value before use. Keep endpoint protection enabled, preserve a backup of the affected game profile, and avoid running the archive if its source cannot be established.
Where this verdict could be wrong4 caveats
- behaviour.offensiveTechniques contains T1543.002, a service-related persistence technique, though behaviour.persistenceIndicators is empty and no malicious runtime verdict corroborates it.
- The file was first submitted 15 days ago, so its history is relatively short.
- All five dropped children have unknown individual verdicts despite droppedChildren.hasMaliciousChild=false.
- contactedHosts=null, so no completed host-reputation cross-check is available.
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 of 74 engines reported a malicious or suspicious result.
- All 17 reporting tier-1 engines returned no detection.
- One completed sandbox run produced no malicious verdict.
- No confirmed malicious child was found among five inspected hashes.
- CIRCL, MalwareBazaar, and YARAify supplied no malware corroboration.
- The sample was first observed only 15 days ago.
- Runtime mapping included T1543.002, although no persistence indicator corroborated it.
- Five dropped or written child hashes remain individually unclassified.
- No complete contacted-host reputation cross-check is available.
Use it only if obtained from the mod's recognized distribution channel and the SHA-256 matches. Keep endpoint protection enabled and back up the game profile before installing third-party mods.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
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
- 5MITRE ATT&CK techniques
- 12spawned processes
- 0network contacts
- 7filesystem & mutex artifacts
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.
- /proc/3563/coredump_filter
- /tmp/hsperfdata_root/3563
- /var/log/auth.log.1.gz
- /var/log/dpkg.log.1.gz
- /var/log/kern.log.1.gz
- /tmp/hsperfdata_root/3563
Files this sample writes at runtime
This file drops 5 children at runtime. None are currently flagged malicious in our cache.
- d87c5f3cdfb5b7c0510e…1ade9eNever scannednever seen before
- 61625fd8b084f70f242d…55abd2Never scannednever seen before
- 50c82f36208ed8040447…2d7843Never scannednever seen before
- 8e8711854186c68e2368…4a3c7cNever scannednever seen before
- 759aafcfa2395ce1b800…2af0f7Never 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.
- 0rule hits recorded
- 0 / 74engines flagged
- 32sources 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 74 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 34 times from 32 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: DrCoconut Dupe Mod 1.21.11 V4.jar.zip — 98fdb55025b8fecd67e314500cb5a8df3f6e47e7020fc9f049b3a3e13896ec09
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — /bin/gzip
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — /bin/sh sh -c "\n\t\tinvoke-rc.d --quiet cups restart > /dev/null\n" logrotate_script "/var/log/cups/*log "
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: coredump_filter — /proc/3563/coredump_filter
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: 3563 — /tmp/hsperfdata_root/3563
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.
YARA rules
No matchesThe rule pass completed without a saved public match.
0 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
- DrCoconut Dupe Mod 1.21.11 V4.jar.zip
- Format
- JAR
- Code signing
- Not applicable to this file type
- Size
- 15.8 KB
- Last analyzed
- Sep 29, 2026, 8:00 AM UTC
98fdb55025b8fecd67e314500cb5a8df3f6e47e7020fc9f049b3a3e13896ec09Safety & 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 DrCoconut Dupe Mod 1.21.11 V4.jar.zip safe?
What is DrCoconut Dupe Mod 1.21.11 V4.jar.zip?
How many antivirus engines detected DrCoconut Dupe Mod 1.21.11 V4.jar.zip?
What is the SHA-256 hash of DrCoconut Dupe Mod 1.21.11 V4.jar.zip?
Is it safe to open or extract DrCoconut Dupe Mod 1.21.11 V4.jar.zip?
How up to date is this analysis of DrCoconut Dupe Mod 1.21.11 V4.jar.zip?
Community
Member reviews and reports for this exact file hash.