File scan report
Verdict Suspicious
Is TGMacro. exe safe? Treat it as suspicious.
Unsigned gaming macro tool flagged by 6 of the 71 antivirus engines that checked it, including two major antivirus engines with generic labels, while sandbox runs showed no…
Read the whole reasonShow less
Why Suspicious? 6 antivirus engines flag it; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
If it came from a link, an attachment or a stranger, delete it.
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
6 of 71 flagged
- Flagged 6
- No detection 65
- No result 4
- Code signing Unsigned
- Test run Completed
- First seen 6mo ago
Chapter 02
Why we think so
3 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Six of the 71 antivirus engines that checked it flag this unsigned .NET macro tool, two of them major, but every label is generic and names no malware family. The file is widely distributed, and sandbox runs only saw it open its developer's web page and save a settings file.
TrendMicro and Trellix both flag the file, but only with generic machine-learning or rule labels, and no family is shared across engines. The executable is unsigned, so no publisher identity backs it. Across five sandbox runs it launched a browser to its developer's 'installed' page, wrote a settings file and created its own program markers, with no named injection target or high-risk technique. None of the 40 contacted hosts we checked is known malicious, and no external malware database lists the hash. Wide distribution over six months points toward a legitimate tool, yet two major detections keep it out of the clean band.
What We Detected
6 of the 71 antivirus engines that checked it flagged this unsigned .NET executable, including TrendMicro-HouseCall (generic MSIL trojan) and TrellixENS (Artemis generic bucket). No engine names a specific malware family, and malware-sample databases and community rule sets have no entry for it.
Threat Behavior
Across five sandbox runs the program opened Microsoft Edge to its developer's post-install page, wrote a settings file and created a program markers named after the developer. No injection into other processes or high-risk techniques were recorded, and none of the contacted hosts we inspected are known malicious. The ad and analytics traffic came from that web page.
What To Do Now
If you got this macro tool from its official developer page, the detections are likely generic false positives, but keep your antivirus enabled and do not add exclusions. If it came from an unknown source, delete it and download a fresh copy from the official site.
Where this verdict could be wrong1 caveat
- The file is widely distributed and the sandbox runs show only a gaming macro opening its developer's web page, so the generic detections may well be false positives.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Widely distributed, with over 2,000 distinct submitters across six months
- Sandbox runs showed no injection or other high-risk behaviour
- None of the contacted hosts we inspected are known malicious
- Malware-sample databases and community rules list no match
- Two major antivirus engines flag the file with generic trojan labels
- The executable carries no digital signature
- Six engines in total report it as malicious
6 sources checked · all complete. See every source
Chapter 03
What it did in our test
It ran in 5 isolated tests; no test environment rated what it did as risky.
Test run summary
Capture complete- 5isolated sandbox runs
- 16sandbox rule tags
- 3spawned processes
- 42network contacts
- 2filesystem & 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: Checked whether it was running on a test computer.
Note: Read the user name of the test computer.
Note: Deleted files or logs during the test run (installers often clean up after themselves).
Note: Talked to servers over the internet during the test run.
Note: Read basic details of the test computer, such as its Windows version.
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 weakening security settings; no setting change was recorded.
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
TGMacro.exe
8d0c5274aa4fc0029ee63911464fcd553cbb8f898214b08705f192b9558288b7
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
software.exe
"C:\Users\<USER>\Desktop\software.exe"
Test run - Evidence 3 of 7: ProcessSeen in the test run
msedge.exe
"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --single-argument https://trksyln.net/projects/tgm-gaming-macro-tgmacro/installed
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
settings.json
C:\Users\<USER>\Desktop\settings.json
Test run - Evidence 5 of 7: Dropped fileWorked out from other results
84a6d489da045d904e4fe6d5ef3cf59d18b033e41ac29eb439cf4aca5c4fce56
A file it created; no rating is saved for it.
Files it created - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
trksyln.net
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
fundingchoicesmessages.google.com
Contacted during the test run.
Test run - +1 more recorded observation
7 facts from the test run. See the full activity list.
Includes 16 mapped techniques, every process, file, registry and network entry and 3 dropped files.
Show the technical evidenceChapter 04
Technical details
6 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 6
- TrellixENS (major engine)Artemis!5C3C2231B01A
- TrendMicro-HouseCall (major engine)Trojan.MSIL.Gen.TL0101H526ZD
- MaxSecureTrojan.Malware.300983.susgen
- Paloaltogeneric.ml
- SkyhighBehavesLike.Win32.Infected.dh
- VBA32Trojan.Win32.Generic
File fingerprint
- Last analyzed
- Oct 18, 2026, 5:10 PM UTC
- SHA-256
8d0c5274aa4fc0029ee63911464fcd553cbb8f898214b08705f192b9558288b7- SHA-1
a1025fdc8676ee922f464f67b87c33f1b2cbeb55- MD5
5c3c2231b01a9b769b94962b73d0286d
About this file
TGMacro.exe is a Win32 EXE file of 969.7 kB.
- Claims to be
- TGMacroFrom the file's own version information, written by whoever built it.
- Original name
- TGMacro.exeMatches the shared file name.
- Type and size
- Win32 EXE · 969.7 kB
- Signer
- UnsignedNo code signature.
- First seen
- Apr 9, 2026On VirusTotal.
- Submitted by
- 2,215 distinct sources
- Packer
- None detected
- Entropy
- 6.25 of 8
First scanned Updated
Verdict history
- Not fully confirmed
- Suspiciousafter 1 more engine flagged it
Ratings change when antivirus engines, our checks or MalwareTips staff learn more about a file.
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 TGMacro.exe safe, or is it malware?
What is TGMacro.exe?
How many antivirus engines detected TGMacro.exe?
What should I do if I already ran TGMacro.exe?
What is the SHA-256 hash of TGMacro.exe?
How up to date is this analysis of TGMacro.exe?
Community
Member reviews and reports for this exact file hash.