MalwareTips

File scan report

Scan another file

Verdict Suspicious

Analyzed , 10 days ago

Is JuanseUnlock.exe safe? Treat it as suspicious.

Six of the 71 antivirus engines that checked it flagged this unsigned executable, including three major antivirus engines, while generic labels and a clean sandbox run prevent…

Read the whole reasonShow less

Why Suspicious? 6 antivirus engines flag it; nothing else confirms it.

Limited evidence · One sign points to a problem; nothing else confirms it.

Don't run it until you know where it came from

If it came from a link, an attachment or a stranger, delete it.

What to do now4 steps

Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.

What to do

  1. Don't run it unless you're sure where it came from.

  2. Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.

  3. If you can't confirm where it came from, delete it. If you need the program, download it again from the publisher's own website.

If you already ran it

  1. Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.

Not sure what to do?

Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.

Paste this report's link in your topic so helpers can see what was found.

Why we think so

Share this file report

JuanseUnlock.exe: Suspicious — MalwareTips file scan

The link always shows the latest result for this exact file (its SHA-256 fingerprint).

Reads the latest antivirus results for this file's hash. Nothing is uploaded.

Antivirus results

6 of 71 flagged

  • Flagged 6
  • No detection 65
  • No result 4
FileJuanseUnlock.exe1.5 MBSHA-256 eef8afdfc11c…643477
  • Code signing Unsigned
  • Test run Completed
  • First seen 1mo ago
6 of the 71 antivirus engines that checked it flag it, including Trend Micro and McAfee.

Chapter 02

Why we think so

5 points against it and 3 in its favour, checked against the scan evidence.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

Analyst conclusion

The labels lack family consensus, no injection target was identified, and the completed sandbox run returned clean, leaving materially mixed evidence.

Where this verdict could be wrong3 caveats
  • The completed sandbox run returned clean and recorded no persistence indicators.
  • Most engines did not flag the file, including Kaspersky, ESET, BitDefender, Avast, and Avira.
  • No packer or high-entropy code was identified, and the major antivirus engines did not agree on a specific family.

These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.

6 sources checked · 5 complete · 1 not needed or not applicable. See every source

Chapter 03

What it did in our test

It ran in our isolated test environment; no test environment rated what it did as risky.

Test run summary

Capture complete
  • 15sandbox rule tags
  • 2spawned processes
  • 0network contacts
  • 7filesystem & mutex artifacts

What the test run showed

What the file did on a test computer

Confirmed in the test run

  • Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).

  • Note: Listed the programs running on the test computer.

  • Note: Deleted files or logs during the test run (installers often clean up after themselves).

  • Note: Read basic details of the test computer, such as its Windows version.

  • Note: Looked through folders on the test computer (most installers do this).

  • Note: Loaded extra code modules while running.

  • Note: Checked which security software was installed on the test computer.

Sandbox labels we could not confirm (common in safe files too)

  • Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.

  • Not confirmed: A sandbox rule tagged this run as recording keystrokes; no keylogging was confirmed.

This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.

Recorded behavior

What happened in the test

Grouped by step. The order is not a timeline.

Seen in the test runWorked out from other results

  1. Input file

    The submitted object

    1
    1. Evidence 1 of 5: FileSeen in the test run

      JuanseUnlock.exe

      eef8afdfc11c9b939b44e8d0ced8afd4ab83b9c5807cb39a3aaf72f6ef643477

      Uploaded file

  2. Processes

    What ran

    2
    1. Evidence 2 of 5: ProcessSeen in the test run

      JuanseUnlock.exe

      "C:\Users\<USER>\Desktop\JuanseUnlock.exe"

      Test run
    2. Evidence 3 of 5: ProcessSeen in the test run

      JuanseUnlock.exe

      "C:\Users\user\Desktop\JuanseUnlock.exe"

      Test run
    3. +1 more recorded observation

  3. Files

    Created or changed

    2
    1. Evidence 4 of 5: Written fileSeen in the test run

      juanseunlock.log

      C:\Users\<USER>\AppData\Roaming\Juansekill\juanseunlock\juanseunlock.log

      Test run
    2. Evidence 5 of 5: Written fileSeen in the test run

      Roaming

      C:\Users\user\AppData\Roaming

      Test run
    3. +1 more recorded observation

5 facts from the test run. See the full activity list.

Chapter 04

Technical details

6 of the 71 antivirus engines that checked it flag it; no publisher signature.

Sources checked

Every check behind this verdict

6 sources checked · 5 complete · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.

SourceStatusResultChecked
Antivirus enginesVirusTotal · 75 enginesCompleteRisk signal: 6 of 71 engines flagged it · 4 gave no result Details for antivirus engines
Sandbox runVirusTotal sandboxesCompleteCombined summary: clean verdict Details for sandbox run
Contacted hostsMalwareTips URL scannerNot neededThe sandbox recorded no contacted hosts to checkNo date recorded
Signature rulesYARAify community rules + MalwareTips rulesComplete1 MalwareTips behaviour rule Details for signature rules
Malware sample databaseabuse.ch MalwareBazaarCompleteNot listed
Known-software referenceCIRCL hashlookupCompleteNo match

Engines that flagged it 6

  • Fortinet (major engine)PossibleThreat.RF
  • Ikarus (major engine)Trojan.Win64.Krypt
  • TrendMicro-HouseCall (major engine)Trojan.Win64.Gen.TL0101J126Z8
  • Elasticmalicious (moderate confidence)
  • GoogleDetected
  • McAfeeDti!EEF8AFDFC11C

File fingerprint

Last analyzed
Oct 16, 2026, 10:37 AM UTC
SHA-256
eef8afdfc11c9b939b44e8d0ced8afd4ab83b9c5807cb39a3aaf72f6ef643477
SHA-1
b3e9280d2bb335589a6b1f7026f89943bb93e7f8
MD5
c2e366892dd5b03c3748c92fe836194c

About this file

JuanseUnlock.exe is a Win32 EXE file of 1.5 MB.

Type and size
Win32 EXE · 1.5 MB
Signer
UnsignedNo code signature.
First seen
Sep 26, 2026On VirusTotal.
Submitted by
23 distinct sources
Packer
None detected
Entropy
6.51 of 8

First scanned

Chapter 05

Questions & answers

Short answers to the 6 questions people ask most about this file.

Is JuanseUnlock.exe safe, or is it malware?
JuanseUnlock.exe is rated Suspicious: some signs point to a problem, but nothing confirms it is harmful. 6 of the 71 antivirus engines that checked it flag it. Don't run it unless you're sure where it came from. If you need the program, download it again from the publisher's own website.
What is JuanseUnlock.exe?
JuanseUnlock.exe is a Windows program, about 1.5 MB. It carries no version information saying what it is or who made it. VirusTotal first saw it on Sep 26, 2026.
How many antivirus engines detected JuanseUnlock.exe?
6 of the 71 antivirus engines that checked it flag JuanseUnlock.exe, including Trend Micro and McAfee. We weigh which engines flagged it and what else the scan found, not just the count.
I already downloaded and ran JuanseUnlock.exe — what should I do?
No infection is confirmed: the rating is a caution, not a malware finding. 1) Check where it came from. If you can't confirm the source, delete it. 2) Run a full scan with your security software. 3) If the scan finds something, follow its removal steps and change passwords you typed on the device since then.
What is the SHA-256 hash of JuanseUnlock.exe?
The SHA-256 fingerprint of JuanseUnlock.exe is eef8afdfc11c9b939b44e8d0ced8afd4ab83b9c5807cb39a3aaf72f6ef643477, and its MD5 is c2e366892dd5b03c3748c92fe836194c. Two files with the same SHA-256 are identical, so use it to check you have exactly this file, not just one with the same name.
How up to date is this analysis of JuanseUnlock.exe?
This report reflects the scan on Oct 16, 2026. A file's fingerprint never changes, but antivirus engines keep learning, so a rating can change later. To get a newer result, scan the file again: we refresh the antivirus results when the saved ones are out of date.
Chapter 06

Community

Member reviews and reports for this exact file hash.

Related file reports

Recent reports on other files with the same rating.

All file reports
Scan another
Check a different file
URL instead?
Check if a link is safe
This report and its SHA-256 fingerprint are public, so the next person who checks the same file gets an instant answer; documents and images are listed by type instead of their file name. A file we had not seen before is uploaded to VirusTotal, whose security partners and subscribers can download it; MalwareTips deletes its own copy after the scan. If you ran this file and are worried, scan your device with up-to-date security software.