Is Metropolis_24.1.xlsx safe?
No antivirus engine detected a threat, and the completed sandbox run found no malicious activity, though the newly observed spreadsheet has limited history.
All 75 antivirus engines returned without a malicious or suspicious detection, including 17 tier-1 engines. One completed sandbox run recorded no malicious verdict, offensive technique, dropped hash, or network contact, although the spreadsheet is newly observed and lacks established prevalence.
266f1c1d090d56b213…fb032f716527cbRecommended next actions
Before opening
Open it only when its sender or download source is one you independently trust.
If you already opened 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 returned without a malicious or suspicious detection, including 17 tier-1 engines. One completed sandbox run recorded no malicious verdict, offensive technique, dropped hash, or network contact, although the spreadsheet is newly observed and lacks established prevalence.
The strongest evidence is unanimous antivirus silence: 0 of 75 engines flagged the spreadsheet, including all 17 tier-1 engines. A completed sandbox run produced no malicious verdict and recorded no MITRE techniques, processes, dropped hashes, or network contacts. MalwareBazaar, YARAify, and CIRCL provided no corroborating hit. Signing is not applicable to an XLSX document, so the absence of a signature carries no weight. Confidence is moderated because the file is newly observed, and complete contacted-host and dropped-child cross-checks are unavailable.
What We Detected
None of the 75 antivirus engines flagged the spreadsheet as malicious or suspicious. This includes 17 tier-1 engines, and there is no named malware-family consensus. MalwareBazaar, YARAify, and CIRCL also returned no matching intelligence.
Threat Behavior
One completed sandbox run produced no malicious verdict. It recorded no MITRE techniques, spawned processes, written files, dropped hashes, persistence indicators, or network contacts. A complete contacted-host reputation result and a separate dropped-child cross-check are unavailable, so those areas cannot be described as independently cleared.
What To Do Now
The evidence supports ordinary use with normal document precautions. Because this file was first observed very recently, open it only if its source and expected contents make sense, keep endpoint protection enabled, and avoid enabling unexpected external content or links.
Where this verdict could be wrong3 caveats
- file.ageDays=0 and prevalence.classification=rare_new mean the sample has very little reputation history.
- contactedHosts=null and droppedChildren=null leave host-reputation and child-file cross-checks unavailable.
- The 4/4 prior 'safe' similarHashes entries match only by file type, not by content, signer, or hash characteristics.
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 engines reported a malicious or suspicious detection
- 17 tier-1 engines reported no detection
- One completed sandbox run had no malicious verdict
- No offensive MITRE techniques or dropped hashes were recorded
- MalwareBazaar, YARAify, and CIRCL returned no hits
- Newly observed file with only 1 submission from 1 source
- No complete contacted-host reputation cross-check is available
- No separate dropped-child result is available
Open the spreadsheet only if it came from an expected source, while keeping endpoint protection enabled. Treat unexpected links, external data prompts, or requests to enable active content as warning signs.
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
- 0MITRE ATT&CK techniques
- 0spawned processes
- 0network contacts
- 0filesystem & mutex artifacts
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
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
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
- Metropolis_24.1.xlsx
- Format
- Office Open XML Spreadsheet
- Code signing
- Not applicable to this file type
- Size
- 1.9 MB
- Last analyzed
- Oct 7, 2026, 9:17 PM UTC
266f1c1d090d56b213d1b4ad822bbf31c55a96f5016ca25739fb032f716527cbSafety & 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 it only when its sender or download source is one you independently trust.
- 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 Metropolis_24.1.xlsx safe?
What is Metropolis_24.1.xlsx?
How many antivirus engines detected Metropolis_24.1.xlsx?
What is the SHA-256 hash of Metropolis_24.1.xlsx?
Is it safe to open Metropolis_24.1.xlsx?
How up to date is this analysis of Metropolis_24.1.xlsx?
Community
Member reviews and reports for this exact file hash.