File scan report
Verdict Malicious
Is 198macros. exe safe? No, we rate this exact file malicious.
36 of the 71 antivirus engines that checked it flag the file, including nine major antivirus engines that label it Lazy or Agent.
Read the whole reasonShow less
Strong evidence · Two or more major antivirus engines agree.
If you already ran it, follow the steps below.
What to do now4 steps
This file is harmful. Don't run it, and remove it.
If you haven't run it
Don't run this file. Delete it, then empty the Recycle Bin.
If you already ran it
Disconnect the device from the internet, then run a full antivirus scan. Microsoft Defender Offline (Windows Security > Virus & threat protection > Scan options) also finds malware that hides while Windows runs.
If you typed passwords on the device after running it, change them from another device you trust.
If the scan keeps finding it, or the device still acts strangely, scan again with a second-opinion scanner from another company; if that doesn't fix it, back up your personal files and reinstall Windows.
If you already ran it, do these in order.
If you opened or installed it
Avoid banking and sign-ins on that device until it is clean. These free MalwareTips guides walk you through it.
- Trojan removal guideClear steps for Windows, Mac and Android. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (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
36 of 71 flagged
- Flagged 36
- No detection 35
- No result 4
- Code signing Unsigned
- Test run Completed
- First seen 9mo ago
Chapter 02
Why we think so
4 points against it and 0 in its favour, checked against the scan evidence.
The reasoning behind this verdict
The sample is unsigned and carries a long-standing malicious reputation.
Nine major antivirus engines independently label the sample malicious, giving a clear consensus on the Lazy family. Behaviour in the test run includes credential-store access and anti-analysis techniques, corroborated by multiple high-severity rules and 30 YARA rules. The file is unsigned, has a negative reputation score, and no benign signer history offsets the detections. Missing host-reputation coverage is noted but does not outweigh the engine and behavioural evidence.
What We Detected
36 of the 71 antivirus engines that checked it flagged the sample, nine of them major. Microsoft labels it Trojan:Win64/Lazy!MTB; Avast, AVG, Avira, F-Secure, Fortinet, GData, Ikarus, Sophos, Symantec and TrendMicro also report malicious. YARAify matched 30 rules focused on debugger and VM detection.
Threat Behavior
The sample contacts raw IPs and exhibits anti-analysis behaviour, consistent with credential-stealing or persistence mechanisms.
What To Do Now
Do not execute the file. Keep security software enabled and submit the sample to threat-intel platforms for further tracking.
- 9 malicious detections from major antivirus engines
- 30 YARA anti-analysis rules matched
- Unsigned executable
- Negative reputation score (-12)
6 sources checked · 5 complete · 1 not needed or not applicable. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 30sandbox rule tags
- 2spawned processes
- 0network contacts
- 11filesystem & 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: Unpacked hidden content while it ran.
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.
Note: Read the user name of the test computer.
Note: Listed the programs running on the test computer.
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as recording keystrokes; no keylogging was confirmed.
Not confirmed: A sandbox rule tagged this run as contacting a server, but no contacted host was recorded.
Not confirmed: A sandbox rule tagged this run as setting up auto-start; no auto-start entry 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.
Threat context
How trojans work
A trojan pretends to be something useful or harmless so that you run it. Once open, it does its real job in the background, from stealing data to opening a back door or downloading more malware.
Bottom line:The disguise is the whole trick, so a trustworthy-looking name or icon means nothing.
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 4: FileSeen in the test run
198macros.exe
a515d5965eaa6d7788f933b8683fa9182debf95e5a81b7f3b41f7e751cd412a9
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 4: ProcessSeen in the test run
software.exe
"C:\Users\<USER>\Desktop\software.exe"
Test run - Evidence 3 of 4: ProcessSeen in the test run
198macros.exe
"C:\Users\user\Desktop\198macros.exe"
Test run - +1 more recorded observation
- 1
Files
Created or changed
- Evidence 4 of 4: Written fileSeen in the test run
Download-1.tmp
C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
Test run
4 facts from the test run. See the full activity list.
Includes 30 mapped techniques and every process, file, registry and network entry.
Show the technical evidenceChapter 04
Technical details
36 of the 71 antivirus engines that checked it flag it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 36
- Avast (major engine)Win64:MalwareX-gen [Misc]
- AVG (major engine)Win64:MalwareX-gen [Misc]
- Avira (major engine)TR/W64.Agent
- F-Secure (major engine)Trojan.TR/W64.Agent
- Fortinet (major engine)W32/PossibleThreat
- GData (major engine)Win64.Trojan.Agent.7XJQOP
- Ikarus (major engine)Trojan.W64.Agent
- Microsoft (major engine)Trojan:Win64/Lazy!MTB
File fingerprint
- Last analyzed
- Sep 5, 2026, 8:28 AM UTC
- SHA-256
a515d5965eaa6d7788f933b8683fa9182debf95e5a81b7f3b41f7e751cd412a9- SHA-1
af7bfb58172fe2201445e99165f7a22daac93b25- MD5
a2e9334ece4010899674af3ad17e3130
About this file
198macros.exe is a Win32 EXE file of 10.2 MB.
- Type and size
- Win32 EXE · 10.2 MB
- Signer
- UnsignedNo code signature.
- First seen
- Jan 23, 2026On VirusTotal.
- Submitted by
- 1,548 distinct sources
- Packer
- None detected
- Entropy
- 6.32 of 8
First scanned
Includes every engine result (75), 31 matched signature rules, PE section entropy and packers and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 8 questions people ask most about this file.
Is 198macros.exe a virus?
What is 198macros.exe?
How many antivirus engines detected 198macros.exe?
What should I do if I already ran 198macros.exe?
How do I remove 198macros.exe?
What kind of malware is 198macros.exe?
What is the SHA-256 hash of 198macros.exe?
How up to date is this analysis of 198macros.exe?
Community
Member reviews and reports for this exact file hash.