MalwareTips

File scan report

Scan another file

Verdict Suspicious

Analyzed , 3 months ago

Is 7zS.sfx.exe safe? Treat it as suspicious.

Two less reliable engines flagged the file while 17 major antivirus engines stayed clean.

Why Suspicious? 2 antivirus engines flag it, but no major engine agrees; 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

Treat as suspicious pending further analysis; isolate and re-verify before any execution.

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

7zS.sfx.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

2 of 70 flagged

  • Flagged 2
  • No detection 68
  • No result 4
File7zS.sfx.exe1.3 MBSHA-256 6472de894c5c…0e6ec6
  • Code signing Unsigned
  • Test run Completed
  • First seen 10y ago
2 of the 70 antivirus engines that checked it flag it, including APEX and Trapmine.

Chapter 02

Why we think so

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

MT AI Engine · Verdict analysis

The reasoning behind this verdict

Analyst conclusion

Common-old prevalence and several clean Joe Sandbox reports create conflicting signals.

Where this verdict could be wrong1 caveat
  • Unsigned status and adversarial comment flag raise suspicion, yet widely seen and long established prevalence and clean Joe Sandbox runs point the other direction.

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 partial. 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
  • 30sandbox rule tags
  • 6spawned processes
  • 2network contacts
  • 40filesystem & 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).

  • Moderate concern: Ran commands or a script on the test computer.

  • Moderate concern: Used an unusual way to talk to a server.

  • Moderate concern: Checked whether it was running on a test computer.

  • Moderate concern: Hid files or windows on the test computer.

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

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

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

  • Not confirmed: A sandbox rule tagged this run as creating a scheduled task; none was recorded.

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

  • Not confirmed: A sandbox rule tagged this run as spreading through USB drives; nothing confirms it.

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 7: FileSeen in the test run

      7zS.sfx.exe

      6472de894c5cb6050fd80cdd893b8772aef71f8bdb5c65a0175cf7cbb90e6ec6

      Uploaded file

  2. Processes

    What ran

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

      program.exe

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

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

      setup.exe

      .\setup.exe

      Test run
    3. +1 more recorded observation

  3. Files

    Created or changed

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

      PatchCleaner.msi

      C:\Users\<USER>\AppData\Local\Temp\7zSEE38.tmp\PatchCleaner.msi

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

      setup.exe

      C:\Users\<USER>\AppData\Local\Temp\7zSEE38.tmp\setup.exe

      Test run
    3. +1 more recorded observation

  4. Network

    Hosts contacted

    2
    1. Evidence 6 of 7: Contacted hostSeen in the test run

      209.197.3.8

      Contacted during the test run.

      Test run
    2. Evidence 7 of 7: Contacted hostSeen in the test run

      8.252.68.126

      Contacted during the test run.

      Test run
    3. +1 more recorded observation

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

Chapter 04

Technical details

2 of the 70 antivirus engines that checked it flag it; no publisher signature.

Sources checked

Every check behind this verdict

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

SourceStatusResultChecked
Antivirus enginesVirusTotal · 74 enginesCompleteRisk signal: 2 of 70 engines flagged it · 4 gave no result Details for antivirus engines
Sandbox runVirusTotal sandboxesCompleteRuntime behaviour was recorded Details for sandbox run
Contacted hostsMalwareTips URL scannerPartial2 hosts contacted in the test run had no completed reputation check Details for contacted hosts
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 2

  • APEXMalicious
  • Trapminemalicious.moderate.ml.score

File fingerprint

Last analyzed
Jul 10, 2026, 11:25 PM UTC
SHA-256
6472de894c5cb6050fd80cdd893b8772aef71f8bdb5c65a0175cf7cbb90e6ec6
SHA-1
4da0e8c2fe1f06b13985d700fe15686a1015c3bb
MD5
70d0bd7633d10c492839272c97b2544e

About this file

7zS.sfx.exe is a Win32 EXE file of 1.3 MB.

Type and size
Win32 EXE · 1.3 MB
Signer
UnsignedNo code signature.
First seen
Mar 3, 2016On VirusTotal.
Submitted by
3,612 distinct sources
Packer
None detected
Entropy
8.00 of 8

First scanned

Chapter 05

Questions & answers

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

Is 7zS.sfx.exe safe, or is it malware?
7zS.sfx.exe is rated Suspicious: some signs point to a problem, but nothing confirms it is harmful. 2 of the 70 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 7zS.sfx.exe?
7zS.sfx.exe is a Windows program, about 1.3 MB. It carries no version information saying what it is or who made it. VirusTotal first saw it on Mar 3, 2016.
How many antivirus engines detected 7zS.sfx.exe?
2 of the 70 antivirus engines that checked it flag 7zS.sfx.exe, including APEX and Trapmine. We weigh which engines flagged it and what else the scan found, not just the count.
What should I do if I already ran 7zS.sfx.exe?
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 7zS.sfx.exe?
The SHA-256 fingerprint of 7zS.sfx.exe is 6472de894c5cb6050fd80cdd893b8772aef71f8bdb5c65a0175cf7cbb90e6ec6, and its MD5 is 70d0bd7633d10c492839272c97b2544e. 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 7zS.sfx.exe?
This report reflects the scan on Jul 10, 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

Other files people checked with the same name, and recent reports with the same rating. A matching name does not make two files the same: only the SHA-256 fingerprint identifies a file.

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.