Is 198macros.exe safe?
Unsigned 10 MB PE with nine tier-1 detections, LSASS access, and 30 YARA anti-analysis rules.
36 of 75 engines flag the file, including nine tier-1 engines that label it Lazy or Agent. Sandbox activity shows LSASS memory access and anti-VM checks, backed by 30 YARA rules. The sample is unsigned and carries a long-standing malicious reputation.
a515d5965eaa6d7788…1f7e751cd412a9Recommended next actions
Before running
Do not run it. Delete this file from the device, then empty the Recycle Bin or Trash.
If you already ran it
Disconnect from the internet, start a full or offline antivirus scan, then secure important accounts from a clean device.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
36 of 75 engines flag the file, including nine tier-1 engines that label it Lazy or Agent. Sandbox activity shows LSASS memory access and anti-VM checks, backed by 30 YARA rules. The sample is unsigned and carries a long-standing malicious reputation.
Nine tier-1 engines independently label the sample malicious, giving a clear consensus on the Lazy family. Runtime behaviour includes credential-store access and anti-analysis techniques, corroborated by multiple high-severity heuristics 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 75 engines flagged the sample, nine of them tier-1. 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
Sandbox execution showed LSASS memory access (T1547.001) and data archiving (T1560). 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 endpoint protection enabled and submit the sample to threat-intel platforms for further tracking.
- 9 tier-1 malicious detections
- LSASS credential-store access observed
- 30 YARA anti-analysis rules matched
- Unsigned executable
- Negative reputation score (-12)
Block the file at the perimeter and endpoint; treat any copies as malicious.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete36 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial3 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete8 signature or behavior rules matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 30MITRE ATT&CK techniques
- 8spawned processes
- 3network contacts
- 11filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Used an input-capture technique that can record credentials or keystrokes.
High concern: Changed an auto-start location that can make code run after sign-in or restart.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Scans through your files and folders.
Moderate concern: Decoded or unpacked concealed content while running.
Moderate concern: Checked the environment for virtualisation or analysis tools.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
Threat context
How trojans work
A trojan disguises itself as something useful or harmless to trick you into running it. Once open, it does its real job in the background — anything 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.
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
198macros.exe
a515d5965eaa6d7788f933b8683fa9182debf95e5a81b7f3b41f7e751cd412a9
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\software.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\services.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Download-1.tmp
C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
04Isolated runtime analysis
Network
Hosts contacted
- Contacted hostObserved
1.1.1.1
Contact observed during runtime.
05Isolated runtime analysis - Contacted hostObserved
8.8.8.8
Contact observed during runtime.
06Isolated runtime analysis - +1 more recorded observation in Analyst mode
6 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
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.
- 1.1.1.1
- 8.8.8.8
- 162.159.36.2
- C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
- Sandboxie_SingleInstanceMutex_Control
- SBIE_BOXED_ServiceInitComplete_Mutex1
- MicrosoftVirtualPC7UserServiceMakeSureWe'reTheOnlyOneMutex
- Frz_State
- AMResourceMutex3
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 8rule hits recorded
- 36 / 75engines flagged
- 1,548sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
6 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
36 of 75 antivirus engines flagged the file, including AhnLab-V3 and alibabacloud.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has a long, established submission history across 1,548 sources.
ProvenanceDerivedSourceSubmission historyObserved at - 04
Scanned file: 198macros.exe — a515d5965eaa6d7788f933b8683fa9182debf95e5a81b7f3b41f7e751cd412a9
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\software.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\services.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Download-1.tmp — C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 1.1.1.1 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 8.8.8.8 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: generic-trojan
One or more independent reference databases matched this hash.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
- BLOWFISH_Constants
- Check_Debugger
- Check_Dlls
- Check_Qemu_Description
- Check_Qemu_DeviceMap
2 engines labelled this sample as anti-VM / anti-debug / sandbox-evading — strong consensus that this is a detonation-guarded malware sample.
EvidenceTrojan.AntiVMSandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.
EvidenceC:\Windows\system32\lsass.exeThe sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence162.159.36.2
36 of 75 engines flagged this file
View all 75 engine results
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
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Fingerprint and provenance
- File name
- 198macros.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 9.7 MB
- Last analyzed
- Sep 5, 2026, 8:28 AM UTC
a515d5965eaa6d7788f933b8683fa9182debf95e5a81b7f3b41f7e751cd412a9Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file is dangerous. Treat it as harmful and remove it.
- Recovery step 01
Don't run this file. Delete this file from the device, then empty the Recycle Bin or Trash.
- Recovery step 02
If you already ran it, disconnect from the internet and start with a full antivirus scan or Microsoft Defender Offline scan. If compromise is suspected or the problem persists, use a reputable second-opinion scanner and follow incident-recovery or clean-reinstall guidance.
- Recovery step 03
From a different, clean device, change the passwords on your important accounts (email and banking first) and turn on two-factor authentication.
- Recovery step 04
Get a fresh copy from the developer's official site or an official app store.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
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.