File scan report
Verdict Suspicious
Is Autosofted_
5 of the 71 antivirus engines that checked it flag this Windows program, but nothing confirms it is harmful.
Why Suspicious? 5 antivirus engines flag it, but no major engine agrees and one sandbox test run rated it malicious while another found nothing.
Moderate evidence · More than one sign points to a problem, but nothing confirms it is harmful.
Do not execute the file on a production or personal system unless it came from a source you can independently verify. Keep security protection enabled and prefer a current, signed alternative for keyboard automation.
What to do now4 steps
Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.
What to do
Don't run it unless you're sure where it came from.
Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.
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
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.
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
5 of 71 flagged
- Flagged 5
- No detection 66
- No result 4
- Code signing Unsigned
- Test run Completed
- First seen 8y ago
Chapter 02
Why we think so
2 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Only 5 of the 71 antivirus engines that checked it flagged it, no major antivirus engines detected it, another sandbox returned clean, and the fully checked network contacts had no known adverse reputation.
Five of the 71 antivirus engines that checked it flagged the executable, but none of the 17 major antivirus engines did, and the labels do not converge on one family. Evidence from the test run is more concerning: the sample mapped to and injected into WMIADAP.EXE and multiple updater processes. That evidence is tempered by a split sandbox result, with one malicious assessment and one clean assessment. The file has also been widely submitted since 2017, and the complete reputation check of its 37 distinct observed contacts found no known adverse hosts. With no malicious child verdict or malware-specific external intelligence corroboration, the evidence supports caution rather than a definitive malware-family attribution.
What We Detected
Five of the 71 antivirus engines that checked it flagged the executable.
Threat Behavior
Two sandbox runs produced conflicting assessments. The other run returned clean. All 37 distinct observed network contacts received reputation coverage, with none known as malicious or suspicious; analysis-VM background contacts were not counted as sample evidence. Ten dropped files lacked saved verdicts, so they provide no positive or negative conclusion.
What To Do Now
Avoid running this unsigned executable on a primary system until its source and integrity are independently verified.
Where this verdict could be wrong5 caveats
- All 17 major antivirus engines returned no detection, and only 5 of the 71 antivirus engines that checked it flagged the file.
- The file is widely observed and has circulated since 2017, which weighs against a newly distributed malware campaign.
- The complete host-reputation cross-check found no known-malicious or suspicious host among the 37 distinct observed contacts.
- One of the two sandbox runs returned clean, so the malicious runtime assessment lacks consensus.
- No malware-specific YARA rules or external intelligence matches corroborated the detections.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- None of the 17 major antivirus engines raised a detection.
- The file has been submitted 45,334 times by 3,703 sources and has been observed since 2017.
- The complete reputation check found no known-malicious or suspicious host among all 37 distinct observed contacts.
- The second sandbox run returned clean.
- No malware-specific external intelligence match or confirmed malicious file it created was found.
- One of two sandbox runs produced a malicious assessment.
- Five engines raised detections, including adware/downloader and AutoitGen worm labels.
6 sources checked · all complete. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; 1 test environment rated what it did as risky.
Test run summary
Capture complete- 34sandbox rule tags
- 11spawned processes
- 19network contacts
- 35filesystem & 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: 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.
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.
Not confirmed: A sandbox rule tagged this run as weakening security settings; no setting change 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.
- 1
Input file
The submitted object
- Evidence 1 of 7: FileSeen in the test run
Autosofted_Auto_Keyboard_Presser_1.9.exe
c21996d9bf78dc7172b5eaca6d2dedbb17ef0f86e9b23a6363550183e52778d8
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
file.exe
"C:\Users\<USER>\Desktop\file.exe"
Test run - Evidence 3 of 7: ProcessSeen in the test run
0007476973.exe
C:\Users\Johnson\AppData\Local\Temp\0007476973.exe
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
Autosofted License.txt
C:\Users\<USER>\AppData\Local\Autosofted License.txt
Test run - Evidence 5 of 7: Written fileSeen in the test run
Autosofted License.txt
C:\Documents and Settings\Administrator\Local Settings\Application Data\Autosofted License.txt
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
api.bing.com
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
ieonline.microsoft.com
Contacted during the test run.
Test run - +1 more recorded observation
7 facts from the test run. See the full activity list.
Includes the sandbox verdicts, 34 mapped techniques, every process, file, registry and network entry and 10 dropped files.
Show the technical evidenceChapter 04
Technical details
5 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.
Engines that flagged it 5
- APEXMalicious
- GridinsoftAdware.Win32.Downloader.ns
- MaxSecureTrojan.Malware.685302649.susgen
- Trapminemalicious.moderate.ml.score
- ZillyaWorm.AutoitGen.Win32.928
File fingerprint
- Last analyzed
- Oct 12, 2026, 5:33 PM UTC
- SHA-256
c21996d9bf78dc7172b5eaca6d2dedbb17ef0f86e9b23a6363550183e52778d8- SHA-1
948d219d89dae0a277519978b751cb70991eb577- MD5
e60e845933d747c615286b762630919a
About this file
Autosofted_Auto_Keyboard_Presser_1.9.exe is a Win32 EXE file of 1.1 MB.
- Type and size
- Win32 EXE · 1.1 MB
- Signer
- UnsignedNo code signature.
- First seen
- Dec 10, 2017On VirusTotal.
- Submitted by
- 3,703 distinct sources
- Packer
- None detected
- Entropy
- 6.68 of 8
First scanned
Includes every engine result (75), 1 matched signature rule, PE section entropy and packers and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is Autosofted_Auto_Keyboard_Presser_1.9.exe safe, or is it malware?
What is Autosofted_Auto_Keyboard_Presser_1.9.exe?
How many antivirus engines detected Autosofted_Auto_Keyboard_Presser_1.9.exe?
I already downloaded and ran Autosofted_Auto_Keyboard_Presser_1.9.exe — what should I do?
What is the SHA-256 hash of Autosofted_Auto_Keyboard_Presser_1.9.exe?
How up to date is this analysis of Autosofted_Auto_Keyboard_Presser_1.9.exe?
Community
Member reviews and reports for this exact file hash.