Is weekly-timesheet-sharepoint.zip safe?
A 764-day-old ZIP archive with zero malicious detections across 78 engines and no sandbox malice.
All 78 engines returned clean, sandbox analysis showed only ambient techniques, and no external-intel or RAG hits exist. The file is a rare but long-standing archive with no malicious indicators.
90f580ef77797924d3…ea2b774f4a0da4Recommended 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.
All 78 engines returned clean, sandbox analysis showed only ambient techniques, and no external-intel or RAG hits exist. The file is a rare but long-standing archive with no malicious indicators.
Zero detections from 78 engines, including 18 tier-1 engines, combined with a clean sandbox run and no external-intel matches, strongly indicate the archive is benign. The low submission count (rare_old) is consistent with a niche internal document rather than malware. No brand mismatch, signing issues, or adversarial flags are present.
What We Detected
78 engines scanned the ZIP; none flagged it malicious. Sandbox execution produced only ambient file-system and process-name changes with no offensive MITRE techniques.
Threat Behavior
No C2 domains, dropped malicious children, or persistence mechanisms were observed. The archive merely lists contents and extracts under standard tools.
What To Do Now
The file can be opened with any standard archive utility. Keep endpoint protection enabled as a general precaution.
- Zero malicious detections across 78 engines
- Clean sandbox verdict
- No external-intel hits
Treat the archive as safe; open normally with built-in ZIP tools while keeping security software active.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 78 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
- 2MITRE ATT&CK techniques
- 6spawned processes
- 0network contacts
- 1filesystem & mutex artifacts
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
weekly-timesheet-sharepoint.zip
90f580ef77797924d39314f995c9fb2aaeccffbdc7a7d6faa7ea2b774f4a0da4
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
/usr/bin/exo-open exo-open /tmp/weekly-timesheet-sharepoint.zip
02Isolated runtime analysis - ProcessObserved
Observed process
/usr/bin/dbus-launch dbus-launch --autolaunch=a39eb3ed78b7401fb6809ed0c562a5b1 --binary-syntax --close-stderr
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
user
/root/.cache/dconf/user
04Isolated runtime analysis
4 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
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.
- /root/.cache/dconf/user
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 / 78engines flagged
- 3sources 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 78 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 5 times from 3 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: weekly-timesheet-sharepoint.zip — 90f580ef77797924d39314f995c9fb2aaeccffbdc7a7d6faa7ea2b774f4a0da4
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — /usr/bin/exo-open exo-open /tmp/weekly-timesheet-sharepoint.zip
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — /usr/bin/dbus-launch dbus-launch --autolaunch=a39eb3ed78b7401fb6809ed0c562a5b1 --binary-syntax --close-stderr
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: user — /root/.cache/dconf/user
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 78 engines flagged this file
View all 78 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Rarely uploaded, but has been around for a while. Often niche legitimate software or old internal tooling; not a strong malware signal on its own.
Fingerprint and provenance
- File name
- weekly-timesheet-sharepoint.zip
- Format
- ZIP
- Code signing
- Not applicable to this file type
- Size
- 438.8 KB
- Last analyzed
- Aug 19, 2026, 2:53 PM UTC
90f580ef77797924d39314f995c9fb2aaeccffbdc7a7d6faa7ea2b774f4a0da4Safety & 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 weekly-timesheet-sharepoint.zip safe?
What is weekly-timesheet-sharepoint.zip?
How many antivirus engines detected weekly-timesheet-sharepoint.zip?
What is the SHA-256 hash of weekly-timesheet-sharepoint.zip?
Is it safe to open or extract weekly-timesheet-sharepoint.zip?
How up to date is this analysis of weekly-timesheet-sharepoint.zip?
Community
Member reviews and reports for this exact file hash.