Suspicious
Unsigned AutoClicker.exe exhibits process injection (T1055), direct IP contacts, and evasion tags but lacks tier-1 engine consensus amid low detections and high prevalence.
1ce7da6f2813c2ad1d…894c9a6ec1The verdict, reasoned out.
Not a rules engine. The MT AI Engine reads every signal we collected, weighs them against history, and commits to an answer.
Few engines flag this file, with no tier-1 detections and 17 tier-1 clean reports, suggesting potential overreach by lower-trust scanners. However, behavioural analysis reveals offensive MITRE techniques including process injection and token manipulation, corroborated by high-severity heuristics. Direct IP contacts bypassing DNS and suspicious process spawns like randomized Google updaters align with malware evasion. Despite common prevalence, the negative reputation and anti-analysis tags tip toward caution. Community notes are split, lacking ground truth.
Each signal cites a concrete token from the evidence the arbiter saw — engine name, MITRE technique, signer string, or an exact count.
Gridinsoft (tier2): Malware.Win64.XWorm.tr
triggeredHeuristics[0].rule 'MalwareTips.Synth.ProcessInjection' fired (T1055)
behaviour.contactedIps length=15 (e.g., '20.99.133.109'), contactedDomains=[]
file.tags: 'detect-debug-environment', 'long-sleeps'
file.reputation: -10
- engines.tier1Malicious=0, 17 tier1 clean
- prevalence.common_old (60742 submissions)
- No malicious dropped children or sandbox verdicts
- No malicious contacted hosts
- Process injection (T1055) heuristic fired
- Direct IP C2 pattern (15 IPs, 0 domains)
- Evasion tags: detect-debug-environment, long-sleeps
- Suspicious fake Google updater processes
- Negative reputation (-10) despite high prevalence
- Gridinsoft tier2 'Malware.Win64.XWorm.tr' detection
Treat as suspicious: do not run, quarantine immediately, and upload to additional sandboxes for confirmation. If needed for automation, seek signed alternatives from trusted sources.
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.
- 20.99.133.109
- 192.229.211.108
- a83f:8110:0:0:1b00:100:2800:0
- 192.168.0.43
- 23.216.81.152
- 131.253.33.203
- 192.168.0.67
- 23.55.140.42
- 20.99.186.246
- 23.198.171.50
- C:\Users\<USER>\AppData\Local\Temp\vthtdci
- C:\Users\<USER>\Desktop\ACLib\playback.ico
- C:\Users\<USER>\Desktop\ACLib\record.ico
- C:\Users\<USER>\Desktop\ACLib\stop.ico
- C:\Users\<USER>\AppData\Local\Temp\dkecqvb
- C:\Users\<USER>\AppData\Local\Temp\vthtdci
- %USERPROFILE%\AppData\Local\Temp\creqhzj
- C:\Windows\System32\spp\store\2.0\cache\cache.dat
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER314C.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER3330.tmp.csv
Files this sample writes at runtime
This file drops 4 children at runtime. None are currently flagged malicious in our cache.
- 6f84c8650acc3464c42d…0f8764Never scannednever seen before
- 5375290e66a20bff81fb…3fe80dNever scannednever seen before
- 9e869f60ea0a0de06c7d…649483Never scannednever seen before
- 59d5e9106e907fa61a56…7287a6Never scannednever seen before
YARA + heuristic rules that fired
A researcher-curated or high-severity heuristic rule matched this sample. These rules target specific malware families and are near-definitive.
MITRE T1055 (Process Injection) observed — CreateRemoteThread / APC / reflective-DLL injection. The payload is being smuggled into a legitimate process to bypass AV hooks.
Evidence"C:\Users\<USER>\Desktop\file.exe"Sample contacted 15 external IP address(es) and zero domains. Benign software virtually always uses DNS; no-DNS direct-IP C2 is a strong malware indicator because it bypasses reputation systems and dodges domain-based blocklists.
Evidence20.99.133.109 · 192.229.211.108 · a83f:8110:0:0:1b00:100:2800:0
2 detections across 75 engines
Section entropy & packers
Section-level entropy and packer detection from the PE header. Nothing suspicious here — entropy is within the normal range for unpacked code.
How often this file shows up in the wild
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Forensic fingerprint
- File name
- AutoClicker.exe
- Size
- 1.13 MB
- MIME type
- (unknown)
- Detected type
- Win32 EXE
- SHA-256
- 1ce7da6f2813c2ad1d2e496be6714e08cd618e6d9fe2df26c2bd4d894c9a6ec1
- MD5
- 913a423f66aa1c41e374e21a911a3c20
- SHA-1
- 449df612d0f02e868992faabfbf4d5d37c727936
- PE imphash
- 161c85364c462057ba28801ac1ad5404
- First seen (VT)
- 3/30/2024, 1:17:12 PM
- Last analysis (VT)
- 5/1/2026, 11:47:18 AM
- First scan (MalwareTips)
- 5/1/2026, 1:21:36 PM
- Last scan (MalwareTips)
- 5/1/2026, 2:11:19 PM
- Community reputation
- -10flagged
Reviews & malware reports(0)
Tell the community what you saw. Tag the sample — Trojan, Adware, False Positive — and share what the file did on your system. Your report helps confirm or dispute the AV verdict.