Threat LensFile scan report

Is Granny.exe safe?

Verdict
Safe

No antivirus engine detected Granny.exe, and its established prevalence, unpacked structure, and limited sandbox observation provide no corroborating malware evidence.

All 74 antivirus engines returned no detection, including 17 tier-1 engines, and the file has been submitted more than 2,000 times. One sandbox run showed no offensive-only techniques, malicious verdict, persistence, dropped files, or network contacts, although the executable lacks a verified signature.

Run with normal care

Use a trusted download source and keep endpoint protection enabled. If provenance is uncertain, compare SHA-256 4871133ada7f623e0ca3128459c99faf6414f5c0177e9eab4dbe80eacf2a3e5f with the publisher's documented hash before execution.

Read the full analysis
Saved file evidenceAntivirus consensus
0of 74 flagged
Flagged 0No detection 74
Digital specimenGranny.exe4871133ada7f623e0c…be80eacf2a3e5f
Size656.5 KB
Code signingUnsigned
SandboxRuntime complete
First seen11mo ago
Evidence3 priority signals
0 of 74 antivirus engines flagged the file.

Recommended next actions

01

Before running

Run it only when it came from the developer's official site or another source you independently trust.

02

If you already ran it

Keep normal device protection enabled and stop if the file behaves unexpectedly.

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.

94%Confidence
Very high
Analyst conclusion

All 74 antivirus engines returned no detection, including 17 tier-1 engines, and the file has been submitted more than 2,000 times. One sandbox run showed no offensive-only techniques, malicious verdict, persistence, dropped files, or network contacts, although the executable lacks a verified signature.

Where this verdict could be wrong3 caveats
  • signing.applicable=true while signing.signed=false, so no verified publisher identity or signer history is available.
  • contactedHosts=null, so no completed host-reputation cross-check is available; however, the sandbox recorded no contacted domains, IPs, or URLs.
  • The sole similarHashes match is imphash-only with signerMatchesSubject=false, making it weak evidence rather than a dependable identity match.

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

Use a trusted download source and keep endpoint protection enabled. If provenance is uncertain, compare SHA-256 4871133ada7f623e0ca3128459c99faf6414f5c0177e9eab4dbe80eacf2a3e5f with the publisher's documented hash before execution.

Scan transparency

Coverage & freshness

4 of 5 complete

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

  • Antivirus

    Complete

    0 of 74 engines flagged the file.

  • Sandbox

    Complete

    1 isolated runtime environment contributed observations.

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

Runtime flight recorder

Capture complete
  • 1isolated sandbox run
  • 6MITRE ATT&CK techniques
  • 1spawned processes
  • 0network contacts
  • 0filesystem & mutex artifacts
Recorded behavior

Attack story

Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.

ObservedDerived

2 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.

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

This file appears low risk based on the evidence available now.

  1. Recovery step 01

    Run it only when it came from the developer's official site or another source you independently trust.

  2. Recovery step 02

    A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.

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

6 evidence-based answers
Is Granny.exe safe?
Evidence-based answer
Granny.exe appears safe. 0 of 74 antivirus engines flagged it. Run it only when it came from the developer's official site or another source you independently trust.
What is Granny.exe?
Evidence-based answer
Granny.exe is a Windows executable program, about 657 KB. Our analysis did not identify a verdict-driving threat signal. A file's name can be reused by different files, so we identify it by its cryptographic hash (below).
How many antivirus engines detected Granny.exe?
Evidence-based answer
None — 0 of 74 antivirus engines flagged Granny.exe. That's reassuring, though it is not proof that a file is safe, so we also weigh its behaviour, identity, and reputation.
What is the SHA-256 hash of Granny.exe?
Evidence-based answer
The SHA-256 hash of Granny.exe is 4871133ada7f623e0ca3128459c99faf6414f5c0177e9eab4dbe80eacf2a3e5f, and its MD5 is a17a665b42ae4c8c5f21ce2c032cf5d3. 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.
Is it safe to run Granny.exe?
Evidence-based answer
Based on the recorded evidence, Granny.exe has a low observed risk. The important caveat is source: make sure you downloaded it from the official website or a trusted store, because attackers sometimes distribute malware-laced copies under a legitimate file's name. If your own antivirus flags it, verify the source and the exact hash before overriding the warning.
How up to date is this analysis of Granny.exe?
Evidence-based answer
This report reflects the scan run on September 20, 2026. Because a file's hash never changes, the identity of Granny.exe 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.