Is AutoClicker-1.1.0.exe safe?
Fourteen of 75 engines flagged this unsigned executable, with five tier-1 detections and two engines naming Pomal alongside process-injection evidence.
The unsigned executable drew 14 detections among 75 engines, including five tier-1 results; Microsoft and TrendMicro both identified Pomal. One sandbox recorded T1055 and T1486, although it issued no malicious runtime verdict and the observed host had no reputation-cache hit.
fb5e4dc3404454e8c9…a1078ab5ac71a8Recommended next actions
Before running
Do not run it. Delete this file from the device, then empty the Recycle Bin or Trash.
If you already ran it
Disconnect from the internet, start a full or offline antivirus scan, then secure important accounts from a clean device.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
The unsigned executable drew 14 detections among 75 engines, including five tier-1 results; Microsoft and TrendMicro both identified Pomal. One sandbox recorded T1055 and T1486, although it issued no malicious runtime verdict and the observed host had no reputation-cache hit.
The strongest evidence is the 14/75 detection count, including five tier-1 engines. Microsoft and TrendMicro independently use the Pomal family name, while DrWeb, Sophos, and Symantec add corroborating trojan detections, though the family consensus is not strong under the three-engine threshold. Runtime evidence maps activity to T1055 process injection and T1486 data-impact behavior, increasing concern beyond static labels. The executable is unsigned and has no established signer history. Counter-signals include a non-malicious sandbox verdict, no confirmed malicious dropped child, and no cached threat reputation for the observed host, but they do not outweigh the engine and behavioral evidence.
What We Detected
Fourteen of 75 antivirus engines flagged the executable. Five tier-1 engines detected it; Microsoft reported Pomal, TrendMicro also reported Pomal, and DrWeb, Sophos, and Symantec supplied additional trojan labels. The file has no digital signature or established publisher history.
Threat Behavior
One completed sandbox run recorded techniques mapped to T1055 process injection and T1486 data-impact behavior. It also observed contact with zclicker.com and its recorded IP; the host-reputation check covered that distinct host and returned no malicious or suspicious cache match. The sandbox itself did not issue a malicious verdict, and none of ten inspected dropped files was confirmed harmful, although all ten child classifications remain unresolved.
What To Do Now
Do not run the executable on a production or personal system. Quarantine or remove it while keeping endpoint protection enabled, and obtain a fresh copy only from a verified official distribution channel if the program is required.
Where this verdict could be wrong5 caveats
- behaviour.hasMaliciousSandboxVerdict=false: the one completed sandbox run did not issue a malicious runtime verdict.
- contactedHosts.inspected=1 found no cache hit for the single distinct observed host, including zclicker.com and its recorded IP.
- droppedChildren.inspected=10 found no confirmed malicious child, although all ten child verdicts remain unknown.
- externalIntel.yaraify.ruleCount=0, externalIntel.circl.hit=false, and externalIntel.malwareBazaar.hit=false provide no researcher-curated corroboration.
- 11 tier-1 engines reported no detection, including BitDefender, ESET-NOD32, Fortinet, Avast, and Avira.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- The completed sandbox did not issue a malicious verdict
- No malicious or suspicious cache match for the observed host
- No confirmed malicious child among 10 inspected drops
- No YARAify, CIRCL, or MalwareBazaar corroboration
- No high-entropy code or recognized packer
- 14/75 antivirus detections
- Five tier-1 malicious detections
- Microsoft and TrendMicro identify Pomal
- T1055 process-injection mapping
- T1486 data-impact mapping
- Unsigned executable with no signer history
Quarantine or delete this copy and keep endpoint protection enabled. If the utility is needed, download it again only from a verified official source and confirm its hash or publisher provenance before use.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete14 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 of 2 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete1 signature or behavior rule matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 14MITRE ATT&CK techniques
- 3spawned processes
- 2network contacts
- 15filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Encrypted files or data, behaviour commonly associated with ransomware.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Scans through your files and folders.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
Threat context
How trojans work
A trojan disguises itself as something useful or harmless to trick you into running it. Once open, it does its real job in the background — anything from stealing data to opening a back door or downloading more malware.
Bottom line:The disguise is the whole trick, so a trustworthy-looking name or icon means nothing.
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
AutoClicker-1.1.0.exe
fb5e4dc3404454e8c93ef659fdd4e047d149d8589c2e64ad55a1078ab5ac71a8
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\AutoClicker-1.1.0.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\cmd.exe /c "ver"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
AutoHotkey.exe
C:\Users\<USER>\AppData\Local\Temp\_MEI26642\Assets\AutoHotkey.exe
04Isolated runtime analysis - Written fileObserved
darkclick.png
C:\Users\<USER>\AppData\Local\Temp\_MEI26642\Assets\darkclick.png
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
zclicker.com
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
104.21.76.231
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- zclicker.com
- 104.21.76.231
- C:\Users\<USER>\AppData\Local\Temp\_MEI26642\Assets\AutoHotkey.exe
- C:\Users\<USER>\AppData\Local\Temp\_MEI26642\Assets\darkclick.png
- C:\Users\<USER>\AppData\Local\Temp\_MEI26642\Assets\darksettings.png
- C:\Users\<USER>\AppData\Local\Temp\_MEI26642\Assets\icon.ico
- C:\Users\<USER>\AppData\Local\Temp\_MEI26642\Assets\lightclick.png
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 48f4a239c25354f0e9f8…17ecedNever scannednever seen before
- 3271d39d7b4dcd841e8e…efe5e5Never scannednever seen before
- cb71909bf01a3a7a4c73…d46e13Never scannednever seen before
- 98074c85650a420a095a…b084e9Never scannednever seen before
- 81eca6840b87f2def9fc…d7aaaaNever scannednever seen before
- 4f05f31ca026bbfeeee4…7ab5deNever scannednever seen before
- 3130bf26da0c840c1e02…5a3539Never scannednever seen before
- 47576cae321c80e69c7f…ac6b91Never scannednever seen before
- 165be658ab7d61ffc3df…d3acd7Never scannednever seen before
- 76f6bc85fc9cb89bc3f9…5415eaNever scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 1rule hit recorded
- 14 / 75engines flagged
- 52sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
14 of 75 antivirus engines flagged the file, including APEX and Bkav.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 58 times from 52 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: AutoClicker-1.1.0.exe — fb5e4dc3404454e8c93ef659fdd4e047d149d8589c2e64ad55a1078ab5ac71a8
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\AutoClicker-1.1.0.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\cmd.exe /c "ver"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: AutoHotkey.exe — C:\Users\<USER>\AppData\Local\Temp\_MEI26642\Assets\AutoHotkey.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: darkclick.png — C:\Users\<USER>\AppData\Local\Temp\_MEI26642\Assets\darkclick.png
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: zclicker.com — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 104.21.76.231 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: generic-trojan
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
Evidence"C:\Users\<USER>\Desktop\AutoClicker-1.1.0.exe"
14 of 75 engines flagged this file
View all 75 engine results
Section entropy & packers
No high-entropy executable section or known packer signature was detected. Data and resource sections can still have high entropy without indicating packed code.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- AutoClicker-1.1.0.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 19.5 MB
- Last analyzed
- Sep 26, 2026, 9:00 PM UTC
fb5e4dc3404454e8c93ef659fdd4e047d149d8589c2e64ad55a1078ab5ac71a8Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file is dangerous. Treat it as harmful and remove it.
- Recovery step 01
Don't run this file. Delete this file from the device, then empty the Recycle Bin or Trash.
- Recovery step 02
If you already ran it, disconnect from the internet and start with a full antivirus scan or Microsoft Defender Offline scan. If compromise is suspected or the problem persists, use a reputable second-opinion scanner and follow incident-recovery or clean-reinstall guidance.
- Recovery step 03
If any of your files were locked or renamed, do NOT pay the ransom — payment rarely restores files. Recover them from a backup instead.
- Recovery step 04
Get a fresh copy from the developer's official site or an official app store.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is AutoClicker-1.1.0.exe malware?
What is AutoClicker-1.1.0.exe?
How many antivirus engines detected AutoClicker-1.1.0.exe?
I already downloaded and ran AutoClicker-1.1.0.exe — what should I do?
How do I remove AutoClicker-1.1.0.exe?
What kind of malware is AutoClicker-1.1.0.exe?
What is the SHA-256 hash of AutoClicker-1.1.0.exe?
How up to date is this analysis of AutoClicker-1.1.0.exe?
Community
Member reviews and reports for this exact file hash.