MalwareTips

File scan report

Scan another file

Verdict Suspicious

Analyzed , 3 months ago

Is ClassicPaint-1.1-setup.exe safe? Treat it as suspicious.

One less reliable engine flagged the sample while 17 major antivirus engines reported clean.

Why Suspicious? One antivirus engine (APEX) flags it; nothing else confirms it.

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

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

Treat as suspicious; avoid execution until additional verification or a signed version is obtained.

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 install 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 installed 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

ClassicPaint-1.1-setup.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

1 of 69 flagged

  • Flagged 1
  • No detection 68
  • No result 4
FileClassicPaint-1.1-setup.exe4.8 MBSHA-256 2e4c7957b523…fc1644
  • Code signing Unsigned
  • Test run Completed
  • First seen 3y ago
1 of the 69 antivirus engines that checked it flags it (APEX).

Chapter 02

Why we think so

3 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

Sandbox behaviour includes multiple offensive MITRE techniques and direct-IP contact to 20 addresses with no domains. Prevalence is widely seen and long established for an unsigned installer, producing mixed signals.

Where this verdict could be wrong1 caveat
  • Unsigned installer with high-entropy sections and direct-IP a control server raises suspicion even at widely seen and long established prevalence; the single less reliable detection alone would be ignored but the sandbox behaviour tips the balance.

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
  • 37sandbox rule tags
  • 8spawned processes
  • 21network 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: Unpacked hidden content while it ran.

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

  • Note: Read the user name of the test computer.

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

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

  • Not confirmed: A sandbox rule tagged this run as password-store access, but nothing touched the Windows password store.

  • 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 creating a service; no new service was recorded.

  • Not confirmed: A sandbox rule tagged this run as setting up auto-start; no auto-start entry was recorded.

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

      ClassicPaint-1.1-setup.exe

      2e4c7957b5230117313dc1aad4c5a71777025ec5476b022a591f930b6efc1644

      Uploaded file

  2. Processes

    What ran

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

      file.exe

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

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

      file.tmp

      "C:\Users\<USER>\AppData\Local\Temp\is-TNV4E.tmp\file.tmp" /SL5="$50026,3888726,886784,C:\Users\<USER>\Desktop\file.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

      file.tmp

      C:\Users\<USER>\AppData\Local\Temp\is-TNV4E.tmp\file.tmp

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

      _setup64.tmp

      C:\Users\<USER>\AppData\Local\Temp\is-IVDL0.tmp\_isetup\_setup64.tmp

      Test run
    3. +1 more recorded observation

  4. Network

    Hosts contacted

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

      13.107.246.38

      Contacted during the test run.

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

      68.183.112.81

      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

1 of the 69 antivirus engines that checked it flags 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 · 73 enginesCompleteWorth noting: 1 of 69 engines flagged it · 4 gave no result Details for antivirus engines
Sandbox runVirusTotal sandboxesCompleteRuntime behaviour was recorded Details for sandbox run
Contacted hostsMalwareTips URL scannerPartial1 of 21 contacted hosts were cross-checked; coverage is incomplete Details for contacted hosts
Signature rulesYARAify community rules + MalwareTips rulesComplete2 MalwareTips behaviour rules Details for signature rules
Malware sample databaseabuse.ch MalwareBazaarCompleteNot listed
Known-software referenceCIRCL hashlookupCompleteNo match

Engines that flagged it 1

  • APEXMalicious

File fingerprint

Last analyzed
Jul 9, 2026, 9:17 AM UTC
SHA-256
2e4c7957b5230117313dc1aad4c5a71777025ec5476b022a591f930b6efc1644
SHA-1
c6340ecd5d566c7372b4f4e4dd709e0b3ae5c011
MD5
a71fe518803220831fd9291032b70fed

About this file

ClassicPaint-1.1-setup.exe is a Win32 EXE file of 4.8 MB.

Type and size
Win32 EXE · 4.8 MB
Signer
UnsignedNo code signature.
First seen
Dec 8, 2022On VirusTotal.
Submitted by
2,210 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 ClassicPaint-1.1-setup.exe safe, or is it malware?
ClassicPaint-1.1-setup.exe is rated Suspicious: some signs point to a problem, but nothing confirms it is harmful. 1 of the 69 antivirus engines that checked it flags it. Don't install it unless you're sure where it came from. If you need the software, download a fresh installer from the developer's own website.
What is ClassicPaint-1.1-setup.exe?
ClassicPaint-1.1-setup.exe is a software installer, about 4.8 MB. It carries no version information saying what it is or who made it. VirusTotal first saw it on Dec 8, 2022.
How many antivirus engines detected ClassicPaint-1.1-setup.exe?
1 of the 69 antivirus engines that checked it flags ClassicPaint-1.1-setup.exe (APEX). We weigh which engines flagged it and what else the scan found, not just the count.
What should I do if I already installed ClassicPaint-1.1-setup.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 ClassicPaint-1.1-setup.exe?
The SHA-256 fingerprint of ClassicPaint-1.1-setup.exe is 2e4c7957b5230117313dc1aad4c5a71777025ec5476b022a591f930b6efc1644, and its MD5 is a71fe518803220831fd9291032b70fed. 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 ClassicPaint-1.1-setup.exe?
This report reflects the scan on Jul 9, 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.