File scan report
Verdict Suspicious
Is Auto Res Changer. exe safe? Treat it as suspicious.
This unsigned, rarely seen display-resolution tool drew 4 of 75 engine detections and split sandbox results, so the evidence is too contradictory to call it safe or harmful.
Read the whole reasonShow less
Why Suspicious? 4 antivirus engines flag it 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.
Avoid running this tool unless it came from a trusted official source. Keep your security software enabled and rescan the file later as more evidence becomes available.
What to do now5 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.
It is only 1 day old. If you're unsure, scan it again in a few days; antivirus engines often catch up on new files.
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
4 of 70 flagged
- Flagged 4
- No detection 66
- No result 5
- Code signing Unsigned
- Test run Completed
- First seen 1d ago
Chapter 02
Why we think so
4 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Four of the 70 antivirus engines that checked it flagged this unsigned program, and only one of them is a major antivirus engine using a generic trojan label. The sandbox results were split between malicious and clean. The recorded activity looks ordinary: the program wrote a settings file and a log file. The file was first seen on Oct 25, 2026, with a single submitter, so there is too little history to settle the question.
Ikarus is the only major antivirus engine to flag the file, and its label is a generic trojan name. Google and two less reliable engines also detected it, while 17 other major antivirus engines reported it clean. The combined sandbox label lists both malware and clean, and no injected process, persistence or malicious network contact was recorded. The only connections observed were Microsoft certificate-list downloads. The file is unsigned and has a single submitter, and no reference database or community rule matches it. The evidence points both ways, so more history or a closer inspection is needed.
What We Detected
4 of the 70 antivirus engines that checked it flagged the file: Ikarus labels it Trojan.Win64.Krypt, Google marks it detected, and two less reliable engines add generic or reputation-based verdicts. 17 major antivirus engines raised nothing. The file is unsigned and was first seen on Oct 25, 2026, with one submitter. The antivirus analysis found no packer.
Threat Behavior
Across 5 sandbox runs, the combined verdict label lists both malware and clean. The program created its own settings folder, a configuration file and a log file, and set a single-instance lock. No injection into another process, no persistence and no suspicious network contact was recorded. Its only connections were Microsoft certificate-revocation downloads.
What To Do Now
Only run this tool if you obtained it from its developer's official source. If you are unsure where it came from, hold off and rescan it later, after more engines and reports have accumulated.
Where this verdict could be wrong2 caveats
- A trojan label from one major antivirus engine plus a malicious sandbox label could mark an early-stage threat that other engines have not yet caught up with.
- The observed activity (a settings file, a log file and a single-instance lock) fits an ordinary display-resolution utility, which argues for a false positive.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 17 major antivirus engines reported it clean
- Another sandbox run returned clean, and no injection or persistence was recorded
- No packing or obfuscation found by the antivirus analysis
- No matches in malware reference databases or community rules
- One major antivirus engine labels it a trojan
- A sandbox run returned a malicious verdict
- Unsigned executable with no publisher identity
- Rarely submitted, first seen on Oct 25, 2026
6 sources checked · all complete. See every source
Chapter 03
What it did in our test
It ran in 5 isolated tests; 1 test environment rated what it did as risky.
Test run summary
Capture complete- 5isolated sandbox runs
- 21sandbox rule tags
- 2spawned processes
- 3network contacts
- 7filesystem & 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.
Note: Listed the programs running on the test computer.
Note: Read basic details of the test computer, such as its Windows version.
Note: Looked through folders on the test computer (most installers do this).
Note: Loaded extra code modules while running.
Note: Checked which security software was installed on 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 setting up auto-start; no auto-start entry was recorded.
Not confirmed: A sandbox rule tagged this run as changing how Windows loads code; nothing confirms it.
Not confirmed: A sandbox rule tagged this run as loading code in memory; nothing confirms it.
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
AutoResChanger.exe
6982e09e029c61d1397baa27ae42c226438e7cbc0b20888f4b9b5d5b393578ef
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
AutoResChanger.exe
"C:\Users\<USER>\Desktop\AutoResChanger.exe"
Test run - Evidence 3 of 7: ProcessSeen in the test run
AutoResChanger.exe
"C:\Users\user\Desktop\AutoResChanger.exe"
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
BaseNamedObjects
\Sessions\1\BaseNamedObjects
Test run - Evidence 5 of 7: Written fileSeen in the test run
config.ini
C:\Users\user\AppData\Roaming\AutoResChanger\config.ini
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
150.171.110.194
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
199.232.214.172
Contacted during the test run.
Test run - +1 more recorded observation
7 facts from the test run. See the full activity list.
What this file did when executed
This file was detonated in 5 sandboxes and the results were split: 1 returned "malicious" and 1 returned "clean".
Sandbox verdicts
2- VT: MALWAREmalicious
- VT: CLEANclean
Techniques observed in the sandbox
21MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1012
- T1027· Obfuscated code
- T1036
- T1045
- T1050
- T1055· Process injection
- T1055.003· Process injection
- T1057· Lists programs
- T1059· Runs commands
- T1060
- T1063
- T1082· System recon
- T1083· Scans your files
- T1112
- T1129· Loads modules
- T1518· Checks your AV
- T1547.001· Auto-start
- T1553
- T1553.002
- T1574· Execution hijack
- T1620· In-memory loading
Observed activity
Processes started
2Programs the file ran, with their command lines.
AutoResChanger.exe"C:\Users\<USER>\Desktop\AutoResChanger.exe"AutoResChanger.exe"C:\Users\user\Desktop\AutoResChanger.exe"
Network contacts
33 hosts, listed as 2 addresses, 3 links. Links show the host and path only.
- IP address
150.171.110.194 - IP address
199.232.214.172 - URL
http://crl.microsoft.com/pki/crl/products/microsoftrootcert.crl - URL
http://crl.microsoft.com/pki/crl/products/WinPCA.crl - URL
http://crl.microsoft.com/pki/crl/products/MicrosoftTimeStampPCA.crl
Files
4Files the file created, changed or deleted.
- Written
\Sessions\1\BaseNamedObjects - Written
C:\Users\user\AppData\Roaming\AutoResChanger\config.ini - Written
C:\Users\user\AppData\Roaming\AutoResChanger\log.txt - Written
C:\Users\user\AppData\Roaming\AutoResChanger
Mutexes
3Named locks a program uses so only one copy runs; malware families often reuse them.
Local\AutoResChanger_SingleInstanceLocal\MSCTF.Asm.MutexDefault1\Sessions\1\BaseNamedObjects\Local\AutoResChanger_SingleInstance
Files this sample writes at runtime
This file drops 1 child at runtime. None are currently flagged malicious in our cache. 1 has no saved verdict and was not checked; that is missing coverage, not a finding.
- 1f2719b100fcc59601f0…4a0ed0Not checkedno saved verdict
Chapter 04
Technical details
4 of the 70 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 4
- Ikarus (major engine)Trojan.Win64.Krypt
- APEXMalicious
- GoogleDetected
- McAfeeDti!6982E09E029C
File fingerprint
- Last analyzed
- Oct 25, 2026, 7:21 PM UTC
- SHA-256
6982e09e029c61d1397baa27ae42c226438e7cbc0b20888f4b9b5d5b393578ef- SHA-1
146dc8f51b1ff20ba259d9fce5daf047a2c04f52- MD5
260e6bccf8369fa60b7d4d6171bfbc40
About this file
AutoResChanger.exe is a Win32 EXE file of 1.3 MB.
- Type and size
- Win32 EXE · 1.3 MB
- Signer
- UnsignedNo code signature.
- First seen
- Oct 25, 2026On VirusTotal.
- Submitted by
- 1 sourceRarely seen: few people have submitted this exact file.
- Packer
- None detected
- Entropy
- 5.37 of 8
First scanned
Antivirus consensus
4 of 70 engines flagged this file
5 of the 75 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
- Tier-118 engines1flagged
- Tier-235 engines1flagged
- Low-trust17 engines2flagged
View all 75 engine results
- APEXMalicious: Malicious
- GoogleMalicious: Detected
- IkarusMalicious: Trojan.Win64.Krypt
- McAfeeDMalicious: ti!6982E09E029C
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- ArcabitClean
- AvastClean
- Avast-MobileNo result
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceClean
- CynetClean
- DeepInstinctClean
- DrWebClean
- ElasticClean
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GridinsoftClean
- huorongClean
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoClean
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisNo result
- TencentClean
- TrapmineClean
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
VirusTotal's sandbox summary maps this run to MITRE T1055 (Process Injection), but no injected process of the sample's own was recorded (the analysis VM's own WMI adapter, crash handlers and Chrome updater are not counted). VirusTotal maps T1055 on about half of all files no engine flags, so the mapping alone is not evidence of injection.
EvidenceT1055 (sandbox MITRE mapping)
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
Barely seen in the wild and first surfaced recently. 4 antivirus detections make that low prevalence materially relevant, but rarity alone is not proof of malware.
Chapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is AutoResChanger.exe safe, or is it malware?
What is AutoResChanger.exe?
How many antivirus engines detected AutoResChanger.exe?
I already downloaded and ran AutoResChanger.exe — what should I do?
What is the SHA-256 hash of AutoResChanger.exe?
How up to date is this analysis of AutoResChanger.exe?
Community
Member reviews and reports for this exact file hash.