Is X-RAY-gildedbedrock.com_.mcpack safe?
No engine among 76 flagged this established MCPACK archive, and its 114 submissions produced no corroborating threat-intelligence match or named malware family.
The archive drew no malicious or suspicious detections from 76 engines, including 18 tier-1 engines. It has also circulated through 109 sources over 572 days without a threat-intelligence match, although no completed runtime or contacted-host analysis is available.
1606503ed2c9ba95e9…14585681842cecRecommended 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 drew no malicious or suspicious detections from 76 engines, including 18 tier-1 engines. It has also circulated through 109 sources over 572 days without a threat-intelligence match, although no completed runtime or contacted-host analysis is available.
The strongest evidence is the complete absence of detections across 76 engines, with all 18 tier-1 engines reporting no threat. The archive is 572 days old and has appeared through 109 distinct sources in 114 submissions, reducing concern that it is an untested new sample. Research intelligence produced no MalwareBazaar, CIRCL, or YARAify match. Code signing is not meaningful for this ZIP/MCPACK file type, so its unsigned status carries no negative weight. Runtime behavior was not observed, and no complete contacted-host reputation result is available, which modestly limits certainty without outweighing the broad static consensus.
What We Detected
No malicious or suspicious result appeared among 76 engines. All 18 tier-1 engines that contributed, including Microsoft, Kaspersky, BitDefender, ESET-NOD32, and Avast, reported no detection, and no engine supplied a malware-family label.
Threat Behavior
No completed sandbox observation is available because behaviour is null, so runtime conduct cannot be characterized. Likewise, contactedHosts is null, meaning there is no complete host-reputation cross-check. Static intelligence found no MalwareBazaar entry, CIRCL match, or YARAify rule hit.
What To Do Now
The broad engine consensus and established submission history support normal use if the pack came from a source you intended to use. Keep endpoint protection enabled, and avoid importing unexpected content packs received through unsolicited links.
Where this verdict could be wrong3 caveats
- behaviour=null, so there is no completed runtime observation to confirm what the archive does when imported.
- contactedHosts=null, meaning no complete contacted-host reputation result is available.
- The filename includes a website-like component and triggeredHeuristics[0].rule=filename_security_software, but this informational filename signal lacks independent malicious corroboration.
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/76 engines reported a malicious or suspicious result.
- All 18 tier-1 engines reported no detection.
- Observed through 109 sources and 114 submissions over 572 days.
- No MalwareBazaar, CIRCL, or YARAify match.
- No brand mismatch or adversarial-text flag was detected.
- No completed runtime observation is available.
- No contacted-host reputation cross-check is available.
- The filename contains a website-like component and triggered an informational security-software filename heuristic.
Use the content pack only if it came from the expected source, while keeping endpoint protection enabled. Recheck it if its contents change or later scans begin producing reputable detections.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 76 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 / 76engines flagged
- 109sources 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 76 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 109 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
No completed runtime observation is available for this file.
ProvenanceDerivedSourceRuntime coverageObserved 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 76 engines flagged this file
View all 76 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
- X-RAY-gildedbedrock.com_.mcpack
- Format
- ZIP
- Code signing
- Not applicable to this file type
- Size
- 23.7 KB
- Last analyzed
- Sep 22, 2026, 9:41 PM UTC
1606503ed2c9ba95e9504662123d13dae8e1e498a101a9d55e14585681842cecSafety & 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 X-RAY-gildedbedrock.com_.mcpack safe?
What is X-RAY-gildedbedrock.com_.mcpack?
How many antivirus engines detected X-RAY-gildedbedrock.com_.mcpack?
What is the SHA-256 hash of X-RAY-gildedbedrock.com_.mcpack?
Is it safe to open or extract X-RAY-gildedbedrock.com_.mcpack?
How up to date is this analysis of X-RAY-gildedbedrock.com_.mcpack?
Community
Member reviews and reports for this exact file hash.