Is AutoClicker-1.0.6.exe safe?
Unsigned executable with one offensive MITRE technique and four low-trust detections but no tier-1 consensus.
Four low-trust engines flagged the file while 14 tier-1 engines remained silent. The sample is unsigned, contains T1486 encryption behaviour, and its imphash matches prior suspicious or malicious PyInstaller bundles.
cc883e28a8d1370b03…36388cc3e31d0cRecommended next actions
Before running
Do not run it until the source and publisher can be verified independently.
If you already ran it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the developer's official site or an official app store.
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.
Four low-trust engines flagged the file while 14 tier-1 engines remained silent. The sample is unsigned, contains T1486 encryption behaviour, and its imphash matches prior suspicious or malicious PyInstaller bundles.
The absence of tier-1 detections and lack of external-intel hits keep the file out of the malicious category. However, the unsigned status, direct-IP contact, and T1486 technique together with imphash matches to previously suspicious samples produce mixed signals that warrant a suspicious verdict rather than safe.
What We Detected
Four of 75 engines reported malicious indicators, all low-trust. No tier-1 engine agreed on a family. The file is unsigned despite being a 30 MB Win32 executable.
Threat Behavior
Sandbox execution showed T1486 (data encrypted for impact) and direct-IP contact to 162.159.36.2 without an associated domain. Ten child files were dropped, none flagged malicious by our cache.
What To Do Now
Do not run the file on production systems. If you need an auto-clicker utility, obtain it from the original developer site and verify the digital signature before execution.
Where this verdict could be wrong1 caveat
- medium prevalence (900 submitters) and 10 dropped children with no malicious verdicts suggest possible commodity PyInstaller bundle rather than confirmed malware.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- no tier-1 detections
- medium prevalence across 900 sources
- no malicious dropped children
- unsigned executable
- T1486 encryption technique observed
- direct-IP contact without domain
- imphash matches prior suspicious samples
Treat as untrusted; obtain a signed version from the legitimate publisher or choose an alternative utility with verified code signing.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete4 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 runtime contact was observed without a completed reputation cross-check.
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
- 12MITRE ATT&CK techniques
- 3spawned processes
- 1network contacts
- 15filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Encrypted files or data, behaviour commonly associated with ransomware.
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.
Moderate concern: Checked the environment for virtualisation or analysis tools.
Note: Listed running processes; both legitimate software and malware may do this.
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.
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.0.6.exe
cc883e28a8d1370b03bcc0cdd34593ea21189214c3bd10e86836388cc3e31d0c
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\AutoClicker-1.0.6.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\_MEI56162\Assets\AutoHotkey.exe
04Isolated runtime analysis - Written fileObserved
darkclick.png
C:\Users\<USER>\AppData\Local\Temp\_MEI56162\Assets\darkclick.png
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
162.159.36.2
Contact observed during runtime.
06Isolated runtime analysis
6 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.
- 162.159.36.2
- C:\Users\<USER>\AppData\Local\Temp\_MEI56162\Assets\AutoHotkey.exe
- C:\Users\<USER>\AppData\Local\Temp\_MEI56162\Assets\darkclick.png
- C:\Users\<USER>\AppData\Local\Temp\_MEI56162\Assets\darksettings.png
- C:\Users\<USER>\AppData\Local\Temp\_MEI56162\Assets\icon.ico
- C:\Users\<USER>\AppData\Local\Temp\_MEI56162\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
- 4 / 75engines flagged
- 900sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
4 of 75 antivirus engines flagged the file, including APEX and Bkav.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 967 times from 900 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: AutoClicker-1.0.6.exe — cc883e28a8d1370b03bcc0cdd34593ea21189214c3bd10e86836388cc3e31d0c
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Users\<USER>\Desktop\AutoClicker-1.0.6.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — C:\Windows\system32\cmd.exe /c "ver"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: AutoHotkey.exe — C:\Users\<USER>\AppData\Local\Temp\_MEI56162\Assets\AutoHotkey.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: darkclick.png — C:\Users\<USER>\AppData\Local\Temp\_MEI56162\Assets\darkclick.png
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 162.159.36.2 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
The sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence162.159.36.2
4 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.0.6.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 29.5 MB
- Last analyzed
- Aug 21, 2026, 1:23 AM UTC
cc883e28a8d1370b03bcc0cdd34593ea21189214c3bd10e86836388cc3e31d0cSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't run it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source. Get a fresh copy from the developer's official site or an official app store.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is AutoClicker-1.0.6.exe safe, or is it malware?
What is AutoClicker-1.0.6.exe?
How many antivirus engines detected AutoClicker-1.0.6.exe?
I already downloaded and ran AutoClicker-1.0.6.exe — what should I do?
How do I remove AutoClicker-1.0.6.exe?
What is the SHA-256 hash of AutoClicker-1.0.6.exe?
How up to date is this analysis of AutoClicker-1.0.6.exe?
Community
Member reviews and reports for this exact file hash.