Is Default mc 1.0.0.mrpack safe?
No engine detected malware in this ZIP archive, including 17 tier-1 products, although its recent appearance and absent runtime data warrant ordinary caution.
The archive received no malicious or suspicious detections from 75 antivirus engines, and all 17 reporting tier-1 products were silent. No external intelligence source matched it, but the file is newly observed and has no completed runtime analysis, so obtain it from a trusted source before opening.
2571a2b277d6583286…f47d3d8bb39ac4Recommended 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 archive received no malicious or suspicious detections from 75 antivirus engines, and all 17 reporting tier-1 products were silent. No external intelligence source matched it, but the file is newly observed and has no completed runtime analysis, so obtain it from a trusted source before opening.
The strongest evidence is the complete absence of detections across 75 antivirus engines, including 17 tier-1 products. Research intelligence produced no MalwareBazaar, CIRCL, or YARA rule match. Code signing is not meaningful for this ZIP archive, so the lack of a signature carries no negative weight. Five previous file-type matches also received benign assessments, although such broad similarity is weak evidence. Confidence is moderated because the file has only one recorded submission, and neither runtime behavior nor contacted-host reputation was assessed.
What We Detected
No malicious or suspicious result was reported by any of the 75 antivirus engines. All 17 reporting tier-1 products, including Avast, BitDefender, ESET-NOD32, Kaspersky, and Microsoft, produced no detection. MalwareBazaar, CIRCL, and YARAify also supplied no threat match.
Threat Behavior
No completed sandbox observation is available, so execution behavior cannot be characterized. The contacted-host cross-check was not completed or saved, meaning there is no complete network-reputation result. The sample is a ZIP archive, making code-signing absence neutral.
What To Do Now
The file is newly observed and has only one recorded submission, so confirm that it came from the expected mod-pack source. Keep endpoint protection enabled, inspect the archive contents before launching included executables or scripts, and rescan if the package changes.
Where this verdict could be wrong3 caveats
- prevalence.classification=rare_new and file.ageDays=0 mean the archive has almost no established history.
- behaviour=null and contactedHosts=null leave runtime activity and contacted-host reputation unassessed.
- The 5/5 safe similarHashes entries use matchKind=filetype, so they do not demonstrate close content or publisher similarity.
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 detection
- 17 tier-1 engines reported no detection
- No MalwareBazaar, CIRCL, or YARAify threat match
- No brand mismatch detected
- No malicious dropped child was reported
- Newly observed file with one recorded submission
- No completed runtime analysis
- No complete contacted-host reputation result
- Archive contents were not independently characterized by the available evidence
Use the archive only if it came from the expected mod-pack source, and keep endpoint protection enabled. Inspect extracted executables or scripts and rescan them separately before use.
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
PartialRuntime data is present, but no completed sandbox environment is recorded.
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 behavior was not available
The report does not treat a missing runtime observation as a clean result.
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
- 1sources 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
No completed runtime observation is available for this file.
ProvenanceDerivedSourceRuntime coverageObserved at - 03
The hash has been submitted 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved 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
Barely seen in the wild and first surfaced recently. That limits reputation evidence, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- Default mc 1.0.0.mrpack
- Format
- ZIP
- Code signing
- Not applicable to this file type
- Size
- 1.6 MB
- Last analyzed
- Sep 28, 2026, 12:02 AM UTC
2571a2b277d65832865fe35907f06d1c65d72d8e272dec5349f47d3d8bb39ac4Safety & 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 Default mc 1.0.0.mrpack safe?
What is Default mc 1.0.0.mrpack?
How many antivirus engines detected Default mc 1.0.0.mrpack?
What is the SHA-256 hash of Default mc 1.0.0.mrpack?
Is it safe to open or extract Default mc 1.0.0.mrpack?
How up to date is this analysis of Default mc 1.0.0.mrpack?
Community
Member reviews and reports for this exact file hash.