Is Terminal_Startup_Diagnostic_Wrapped (2).zip safe?
Two of 75 engines flagged this newly observed ZIP, but tier-1 engines found nothing and no runtime or researcher evidence corroborates either detection.
Elastic and Sangfor flagged the archive, while all reporting tier-1 engines remained silent and no family consensus formed. Because the ZIP is newly observed, contains a PE, and lacks completed runtime analysis, it should remain quarantined until its contents are inspected or rescanned.
fb3dee9731f4e5fae4…30b5b13afceb60Recommended next actions
Before opening or extracting
Do not open or extract it until the source can be verified independently.
If you already opened or extracted it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the original trusted source and verify its exact hash when possible.
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.
Elastic and Sangfor flagged the archive, while all reporting tier-1 engines remained silent and no family consensus formed. Because the ZIP is newly observed, contains a PE, and lacks completed runtime analysis, it should remain quarantined until its contents are inspected or rescanned.
Only 2 of 75 engines detected the archive, and both detections came from tier-2 products rather than tier-1 engines. The labels do not establish a consistent malware family, with Elastic giving a generic assessment and Sangfor naming Save. No external research source corroborated the detections, but this absence does not prove the archive is benign. The sample is newly observed, has only one submission, and reportedly contains a Windows executable. No completed sandbox observation or comprehensive contacted-host reputation check is available, so uncertainty remains substantial.
What We Detected
Elastic and Sangfor flagged the archive, producing 2 detections among 75 engines. None of the reporting tier-1 engines detected it, and there is no tier-1 family consensus. External checks found no MalwareBazaar record, CIRCL match, or YARAify rule match.
Threat Behavior
No completed sandbox data is available, so execution behavior was not observed. The archive is tagged as containing a PE, but the payload provides no verified behavior, malicious dropped child, or complete contacted-host reputation result. The sample is also newly observed and has only one recorded submission.
What To Do Now
Keep the archive quarantined and do not execute its embedded program on a production system. Obtain it again from a verified source, inspect and scan the extracted contents individually, and rescan after engines have had time to analyze the new sample.
Where this verdict could be wrong3 caveats
- Elastic and Sangfor both flagged the archive, including Sangfor's Trojan.Win32.Save.a label, so the detections cannot be dismissed as low-trust noise.
- The file is zero days old and contains a PE according to file.tags, leaving too little history to establish normal distribution.
- The 5/5 prior safe similarHashes are matchKind=filetype only; sharing the ZIP format is not meaningful content-level 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.
- engines.tier1Malicious=0
- 15 tier-1 engines reported no detection
- engines.tier1FamilyConsensus.family=null
- externalIntel.yaraify.ruleCount=0
- No MalwareBazaar or CIRCL hit
- 2/75 engine detections from Elastic and Sangfor
- Newly observed sample with one source and one submission
- ZIP archive tagged as containing a PE
- No completed runtime observation
- No complete contacted-host reputation result
Keep protection enabled and leave the archive quarantined. Verify its source, scan each extracted component without running it, and wait for additional engine coverage before considering execution.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete2 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
- 2 / 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
2 of 75 antivirus engines flagged the file, including Elastic and Sangfor.
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.
2 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. 2 antivirus detections make that low prevalence materially relevant, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- Terminal_Startup_Diagnostic_Wrapped (2).zip
- Format
- ZIP
- Code signing
- Not applicable to this file type
- Size
- 326.4 KB
- Last analyzed
- Sep 29, 2026, 4:38 PM UTC
fb3dee9731f4e5fae43ce853489c97a5f69bdaf1bc8c9a43bc30b5b13afceb60Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't open or extract it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this archive and use a fresh copy from a trusted source. Get a fresh copy from the original trusted source and verify its exact hash when possible.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is Terminal_Startup_Diagnostic_Wrapped (2).zip safe, or is it malware?
What is Terminal_Startup_Diagnostic_Wrapped (2).zip?
How many antivirus engines detected Terminal_Startup_Diagnostic_Wrapped (2).zip?
What should I do if I already opened or extracted Terminal_Startup_Diagnostic_Wrapped (2).zip?
How do I remove Terminal_Startup_Diagnostic_Wrapped (2).zip?
What is the SHA-256 hash of Terminal_Startup_Diagnostic_Wrapped (2).zip?
How up to date is this analysis of Terminal_Startup_Diagnostic_Wrapped (2).zip?
Community
Member reviews and reports for this exact file hash.