Threat LensFile scan report

Is Terminal_Startup_Diagnostic_Wrapped (2).zip safe?

Verdict
Suspicious

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.

Do not open or extract it until verified

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.

Read the full analysis
Saved file evidenceAntivirus consensus
2of 75 flagged
Flagged 2No detection 73
Digital specimenTerminal_Startup_Diagnostic_Wrapped (2).zipfb3dee9731f4e5fae4…30b5b13afceb60
Size326.4 KB
Code signingNot applicable
SandboxPartial coverage
First seenToday
Evidence2 priority signals
2 of 75 antivirus engines flagged the file, including Elastic and Sangfor.

Recommended next actions

01

Before opening or extracting

Do not open or extract it until the source can be verified independently.

02

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.

Chapter 02

Intelligence

The saved assessment, checked against the scan evidence and recorded coverage.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.

72%Confidence
High
Analyst conclusion

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.

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.

Recommended action

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.

Scan transparency

Coverage & freshness

3 of 5 complete

Complete means the check returned a usable result. It does not mean the file is safe.

  • Antivirus

    Complete

    2 of 75 engines flagged the file.

  • Sandbox

    Partial

    Runtime data is present, but no completed sandbox environment is recorded.

  • Network

    Not run

    No contacted-host reputation check is recorded.

    No timestamp recorded
  • YARA

    Complete

    Rule evaluation completed with no recorded matches.

  • External intel

    Complete

    3 of 3 independent reference sources completed.

Chapter 03

Behavior

Plain-English impact first, then the observed runtime evidence.

Chapter 04

Detection & Forensics

Consensus, attribution, signatures, code structure, prevalence, and identity.

Chapter 05

Safety & 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.

  1. Recovery step 01

    Don't open or extract it unless you're certain it came from a source you trust.

  2. Recovery step 02

    Check where you got it — an unexpected attachment or a random download link is a red flag.

  3. 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.

  4. 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.

7 evidence-based answers
Is Terminal_Startup_Diagnostic_Wrapped (2).zip safe, or is it malware?
Evidence-based answer
Terminal_Startup_Diagnostic_Wrapped (2).zip is suspicious — treat it as unsafe until you're sure. 2 of 75 antivirus engines flag it; that detection signal contributes to the cautious verdict. Don't open or extract it unless you fully trust where it came from. Get a fresh copy from the original trusted source and verify its exact hash when possible.
What is Terminal_Startup_Diagnostic_Wrapped (2).zip?
Evidence-based answer
Terminal_Startup_Diagnostic_Wrapped (2).zip is a compressed archive (application/x-zip-compressed), about 326 KB. We identify a file by its cryptographic hash rather than its name, because the same filename can be reused by completely different files — the hash below is the reliable fingerprint.
How many antivirus engines detected Terminal_Startup_Diagnostic_Wrapped (2).zip?
Evidence-based answer
2 of 75 antivirus engines flagged Terminal_Startup_Diagnostic_Wrapped (2).zip, 2 of them as outright malicious. The raw count alone does not establish safety or danger; we also weigh which engines flagged it and corroborating behavior, identity, reputation, and rule evidence.
What should I do if I already opened or extracted Terminal_Startup_Diagnostic_Wrapped (2).zip?
Evidence-based answer
Act quickly. 1) Disconnect the device from the internet to stop the malware communicating or spreading. 2) Run a full scan with reputable anti-malware software (such as Malwarebytes) and quarantine everything it finds. 3) Change your important passwords from a DIFFERENT, clean device — many threats log keystrokes or steal saved credentials. 4) If you bank or shop on this device, watch closely for fraud and alert your bank. 5) For a confirmed infection, the most reliable fix is to back up your personal files and reinstall the operating system for a clean start.
How do I remove Terminal_Startup_Diagnostic_Wrapped (2).zip?
Evidence-based answer
To remove Terminal_Startup_Diagnostic_Wrapped (2).zip: 1) restart into Safe Mode (Safe Mode with Networking if you need to download a tool) so the malware doesn't auto-start. 2) Run a full scan with reputable anti-malware software and let it quarantine or delete the detections. 3) Delete this archive from the device, then empty the Recycle Bin or Trash. 4) Check your browser extensions, startup items, and scheduled tasks for anything unfamiliar. 5) Reboot and scan again to confirm it's gone. If detections keep coming back, a clean operating-system reinstall is the most dependable cure.
What is the SHA-256 hash of Terminal_Startup_Diagnostic_Wrapped (2).zip?
Evidence-based answer
The SHA-256 hash of Terminal_Startup_Diagnostic_Wrapped (2).zip is fb3dee9731f4e5fae43ce853489c97a5f69bdaf1bc8c9a43bc30b5b13afceb60, and its MD5 is 1ed54160c5dc52bbf044fcf5876329bb. This hash is the file's unique fingerprint — two files with the same SHA-256 are identical. Use it to confirm you're looking at exactly this file (not just one with the same name) when comparing against antivirus databases or a download's published checksum.
How up to date is this analysis of Terminal_Startup_Diagnostic_Wrapped (2).zip?
Evidence-based answer
This report reflects the scan run on September 29, 2026. Because a file's hash never changes, the identity of Terminal_Startup_Diagnostic_Wrapped (2).zip is fixed — but antivirus coverage improves over time, so a file that looks clean today can pick up detections later (and vice-versa). If you need the latest picture, MalwareTips staff can re-run the analysis from scratch.
Chapter 06

Community

Member reviews and reports for this exact file hash.

The raw file is processed temporarily and is not retained after processing. Its hash and report are public and permanent, so the next person who checks the same file gets an instant answer. Unknown files may be submitted to VirusTotal for analysis. If you ran this file on your computer and are worried, scan your system with an up-to-date antivirus and change critical passwords from a different device.