MalwareTips

File scan report

Scan another file

Verdict Suspicious

Analyzed , 12 days ago

Is AutoClicker.exe safe? Treat it as suspicious.

The XWorm label has weak corroboration: only 2 of the 71 antivirus engines that checked it flagged the file, none were major, and one completed sandbox returned clean.

Read the whole reasonShow less

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

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

AutoClicker.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 71 flagged

  • Flagged 2
  • No detection 69
  • No result 4
FileAutoClicker.exe1.2 MBSHA-256 1ce7da6f2813…9a6ec1
  • Code signing Unsigned
  • Test run Completed
  • First seen 2y ago
2 of the 71 antivirus engines that checked it flag it, including Gridinsoft and Bkav.

Chapter 02

Why we think so

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

MT AI Engine · Verdict analysis

The reasoning behind this verdict

Analyst conclusion

Only 2 of the 71 antivirus engines that checked it flagged the sample, with Gridinsoft naming XWorm and Bkav providing a generic label. None of the 17 major antivirus engines raised an alert, and no major family consensus or malware-specific external rule supported XWorm. The file has circulated extensively for more than two years, and its completed sandbox run returned clean. The executable is unsigned, so no authenticated publisher identity explains those capabilities. These conflicting signals support caution rather than accepting either the isolated family label or the clean indicators at face value.

Where this verdict could be wrong2 caveats
  • The program is unsigned, so its publisher and provenance cannot be authenticated.
  • Runtime monitoring recorded injection into two updater processes and token-manipulation techniques, which ordinary click automation does not clearly require.

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 · all complete. 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
  • 29sandbox rule tags
  • 8spawned processes
  • 2network contacts
  • 30filesystem & 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: Downloaded a file during the test run.

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

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

  • Note: Read the network settings of the test computer.

  • Note: Read the user name of 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.

  • 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

      AutoClicker.exe

      1ce7da6f2813c2ad1d2e496be6714e08cd618e6d9fe2df26c2bd4d894c9a6ec1

      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

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

      vthtdci

      C:\Users\<USER>\AppData\Local\Temp\vthtdci

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

      playback.ico

      C:\Users\<USER>\Desktop\ACLib\playback.ico

      Test run
    3. +1 more recorded observation

  4. Network

    Hosts contacted

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

      ocsps.ssl.com

      Contacted during the test run.

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

      23.219.78.68

      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 71 antivirus engines that checked it flag it; no publisher signature.

Sources checked

Every check behind this verdict

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

SourceStatusResultChecked
Antivirus enginesVirusTotal · 75 enginesCompleteRisk signal: 2 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 scannerComplete23 contacted hosts checked 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

  • BkavW32.Malware.F901B55D
  • GridinsoftMalware.Win64.XWorm.tr

File fingerprint

Last analyzed
Oct 14, 2026, 1:02 AM UTC
SHA-256
1ce7da6f2813c2ad1d2e496be6714e08cd618e6d9fe2df26c2bd4d894c9a6ec1
SHA-1
449df612d0f02e868992faabfbf4d5d37c727936
MD5
913a423f66aa1c41e374e21a911a3c20

About this file

AutoClicker.exe is a Win32 EXE file of 1.2 MB.

Type and size
Win32 EXE · 1.2 MB
Signer
UnsignedNo code signature.
First seen
Mar 30, 2024On VirusTotal.
Submitted by
3,732 distinct sources
Packer
None detected
Entropy
6.39 of 8

First scanned Updated

Verdict history

  1. Not fully confirmed
  2. Safeafter a new scan
  3. Suspiciousafter a new scan

Ratings change when antivirus engines, our checks or MalwareTips staff learn more about a file.

Chapter 05

Questions & answers

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

Is AutoClicker.exe safe, or is it malware?
AutoClicker.exe is rated Suspicious: some signs point to a problem, but nothing confirms it is harmful. 2 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 AutoClicker.exe?
AutoClicker.exe is a Windows program, about 1.2 MB. It carries no version information saying what it is or who made it. VirusTotal first saw it on Mar 30, 2024.
How many antivirus engines detected AutoClicker.exe?
2 of the 71 antivirus engines that checked it flag AutoClicker.exe, including Gridinsoft and Bkav. We weigh which engines flagged it and what else the scan found, not just the count.
I already downloaded and ran AutoClicker.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 AutoClicker.exe?
The SHA-256 fingerprint of AutoClicker.exe is 1ce7da6f2813c2ad1d2e496be6714e08cd618e6d9fe2df26c2bd4d894c9a6ec1, and its MD5 is 913a423f66aa1c41e374e21a911a3c20. 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 AutoClicker.exe?
This report reflects the scan on Oct 14, 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.