Is donut-smp-mod-2.0.0 (1).jar safe?
No antivirus engine detected the established JAR, and its completed sandbox run produced no malicious verdict despite two behavior techniques worth noting.
All 75 antivirus engines were free of detections, including 17 tier-1 engines, and one completed sandbox run produced no malicious verdict. Two offensive MITRE techniques and four unknown child-file verdicts warrant ordinary caution, but they are not corroborated by malware intelligence, persistence indicators, or engine detections.
16bd046fad4d732093…ae551095e2f9c7Recommended next actions
Before opening or running
Open or run it only when its publisher and download source have been independently verified.
If you already opened or ran 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 one completed sandbox run produced no malicious verdict. Two offensive MITRE techniques and four unknown child-file verdicts warrant ordinary caution, but they are not corroborated by malware intelligence, persistence indicators, or engine detections.
The strongest evidence is the absence of detections across 75 antivirus engines, including 17 tier-1 engines. The file is also established rather than newly encountered, with 218 submissions from 195 sources over 218 days. One completed sandbox run produced no malicious verdict, and no persistence indicators or network contacts were recorded during that observation. Static and runtime mapping nevertheless associated the activity with T1543.002 and T1562.001, so those behaviors should not be ignored. Four written child files were inspected without a malicious result, although their individual verdicts remain unknown. No complete contacted-host reputation result is available, but there were no observed domains, IP addresses, or URLs requiring that cross-check.
What We Detected
The JAR received 0 detections from 75 antivirus engines, with engines.tier1Malicious=0 and 17 tier-1 engines reporting no detection. It has been submitted 218 times by 195 sources over 218 days, providing substantial exposure without a malware label. CIRCL, MalwareBazaar, and YARAify supplied no corroborating hit.
Threat Behavior
One completed sandbox run produced no malicious verdict and recorded no contacted domains, IP addresses, or URLs. The activity was mapped to T1543.002 and T1562.001, which can indicate service manipulation or impairment of defenses, but no persistence indicators were recorded and no engine corroborated those mappings. Four child files were inspected; none was identified as malicious, though their individual verdicts remain unknown. Because contactedHosts is null, no separate host-reputation result is available.
What To Do Now
Use the JAR only if it came from the expected mod distribution channel and matches the publisher-provided SHA-256 value. Keep endpoint protection enabled, and avoid granting unnecessary administrator privileges or bypassing security warnings.
Where this verdict could be wrong3 caveats
- behaviour.offensiveTechniques includes T1543.002 and T1562.001, techniques associated with service manipulation and impairment of defenses.
- droppedChildren.children contains four files with unknown verdicts, so droppedChildren.hasMaliciousChild=false does not establish that those files are benign.
- contactedHosts=null, meaning no complete host-reputation cross-check is available; however, the observed runtime contact lists were empty.
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 malicious or suspicious results.
- 17 tier-1 engines reported no detection and engines.tier1Malicious=0.
- behaviour.hasMaliciousSandboxVerdict=false in one completed sandbox run.
- No persistence indicators or observed network contacts were recorded.
- 195 sources submitted the sample 218 times over 218 days without external-intelligence hits.
- behaviour.offensiveTechniques includes T1543.002 and T1562.001.
- Four droppedChildren.children entries have unknown individual verdicts.
- contactedHosts=null, so no complete host-reputation cross-check is available.
- JAR code signing is not applicable here, leaving no publisher certificate to authenticate origin.
The file may be used if its source and SHA-256 match the official mod release. Keep endpoint protection enabled and avoid unnecessary elevated permissions.
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
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
- 11MITRE ATT&CK techniques
- 11spawned processes
- 0network contacts
- 13filesystem & 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.
- C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\5624
- C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.timestamp
- C:\ProgramData\Oracle\Java\.oracle_jre_usage\17dfc292991c8786.timestamp
- C:\Users\user\AppData\Local\Temp\hsperfdata_user
- C:\Users\user\AppData\Local\Temp\hsperfdata_user\1972
- C:\Users\user\AppData\Local\Temp\hsperfdata_user\2216
- /tmp/hsperfdata_root/4992
Files this sample writes at runtime
This file drops 4 children at runtime. None are currently flagged malicious in our cache.
- 18dff415eb978fe2a42f…cfa920Never scannednever seen before
- 379b25e278f2af39d7e9…a8c4ecNever scannednever seen before
- d87c5f3cdfb5b7c0510e…1ade9eNever scannednever seen before
- 44a3bab2c338e3bca24c…d3b9e7Never 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 / 75engines flagged
- 195sources 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 195 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
The hash has been submitted 218 times from 195 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: donut-smp-mod-2.0.0 (1).jar — 16bd046fad4d732093cf37d0d50cd5d734fef3015d6eb3eafaae551095e2f9c7
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Program Files\Java\jre-1.8\bin\java.exe" -jar "C:\Users\<USER>\Desktop\sample.jar"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\icacls.exe C:\ProgramData\Oracle\Java\.oracle_jre_usage /grant "everyone":(OI)(CI)M
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: 5624 — C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\5624
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: 3903daac9bc4a3b7.timestamp — C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.timestamp
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 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
- donut-smp-mod-2.0.0 (1).jar
- Format
- JAR
- Code signing
- Not applicable to this file type
- Size
- 9.4 KB
- Last analyzed
- Oct 1, 2026, 4:10 PM UTC
16bd046fad4d732093cf37d0d50cd5d734fef3015d6eb3eafaae551095e2f9c7Safety & 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 run it only when its publisher and download source have 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 donut-smp-mod-2.0.0 (1).jar safe?
What is donut-smp-mod-2.0.0 (1).jar?
How many antivirus engines detected donut-smp-mod-2.0.0 (1).jar?
What is the SHA-256 hash of donut-smp-mod-2.0.0 (1).jar?
Is it safe to open or run donut-smp-mod-2.0.0 (1).jar?
How up to date is this analysis of donut-smp-mod-2.0.0 (1).jar?
Community
Member reviews and reports for this exact file hash.