Is AolAod.exe safe?
Unsigned executable with sandbox evidence of process injection and LSASS access but only one low-tier detection.
One tier-2 engine flagged the file with a generic label; sandbox recorded T1055 and LSASS access. No tier-1 consensus or external-intel hits exist, leaving the sample in mixed-signal territory.
991111a0a9afdc9398…27285083cf8082Recommended next actions
Before running
Do not run it until the source and publisher can be verified independently.
If you already ran it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the developer's official site or an official app store.
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.
One tier-2 engine flagged the file with a generic label; sandbox recorded T1055 and LSASS access. No tier-1 consensus or external-intel hits exist, leaving the sample in mixed-signal territory.
The file is unsigned and shows sandbox activity consistent with process injection and credential-dumping techniques. Only a single tier-2 engine raised a generic detection, while 14 tier-1 engines remained silent. Medium prevalence over many years and the absence of no complete contacted-host reputation result was available or malicious call.
What We Detected
74 engines scanned the sample; only Kingsoft (tier-2) returned a malicious result labeled 'malware.kb.a.999'. 14 tier-1 engines reported clean. The binary is unsigned and contains no packers.
Threat Behavior
Sandbox execution revealed MITRE T1055 (process injection) and direct access to lsass.exe. Two external IP addresses were contacted without domain names. No dropped children or persistence mechanisms were recorded.
What To Do Now
Keep endpoint protection enabled. Do not run the file on production systems until further reputation data or updated engine coverage becomes available.
Where this verdict could be wrong1 caveat
- Single tier-2 detection with generic label and no tier-1 corroboration; 14 tier-1 engines reported clean.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 14 tier-1 engines reported clean
- No tier-1 family consensus
- Medium prevalence over 20 years
- Unsigned executable
- Sandbox evidence of process injection (T1055)
- LSASS memory access observed
- Direct-IP network traffic
Treat the file as untrusted; run it only in an isolated environment or wait for additional engine coverage before any wider deployment.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial2 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete3 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
- 17MITRE ATT&CK techniques
- 13spawned processes
- 2network contacts
- 18filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Changed an auto-start location that can make code run after sign-in or restart.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Removed execution artefacts or logs, which can conceal activity.
Moderate concern: Scans through your files and folders.
Note: Inspects your network configuration.
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.
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
AolAod.exe
991111a0a9afdc939872267d0fad05d32330f4cca50b6b397427285083cf8082
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\executable.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\executable.exe" -put_icons
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Caches
C:\Users\user\AppData\Local\Microsoft\Windows\Caches
04Isolated runtime analysis
Network
Hosts contacted
- Contacted hostObserved
20.99.133.109
Contact observed during runtime.
05Isolated runtime analysis - Contacted hostObserved
23.216.147.76
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.
- 20.99.133.109
- 23.216.147.76
- C:\Users\user\AppData\Local\Microsoft\Windows\Caches
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER1817.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER18F1.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER1921.tmp.txt
- C:\Windows\System32\spp\store\2.0\cache\cache.dat
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER3786.tmp.WERInternalMetadata.xml
- Gtek/AOD Is Working/mutex
- Global\OneSettingQueryMutex+compat+encapsulation
- ZonesCounterMutex
- ZonesCacheCounterMutex
- ZonesLockedCacheCounterMutex
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 3rule hits recorded
- 1 / 74engines flagged
- 5sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
1 of 74 antivirus engines flagged the file, including Kingsoft.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 10 times from 5 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: AolAod.exe — 991111a0a9afdc939872267d0fad05d32330f4cca50b6b397427285083cf8082
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\executable.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\<USER>\Desktop\executable.exe" -put_icons
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Caches — C:\Users\user\AppData\Local\Microsoft\Windows\Caches
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 20.99.133.109 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 23.216.147.76 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for 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.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
EvidenceC:\Windows\System32\svchost.exe -k NetworkService -pSandbox 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.
Evidence20.99.133.109 · 23.216.147.76
1 of 74 engines flagged this file
View all 74 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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- AolAod.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 157.0 KB
- Last analyzed
- Aug 19, 2026, 3:41 AM UTC
991111a0a9afdc939872267d0fad05d32330f4cca50b6b397427285083cf8082Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't run it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source. Get a fresh copy from the developer's official site or an official app store.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is AolAod.exe safe, or is it malware?
What is AolAod.exe?
How many antivirus engines detected AolAod.exe?
What should I do if I already ran AolAod.exe?
How do I remove AolAod.exe?
What is the SHA-256 hash of AolAod.exe?
How up to date is this analysis of AolAod.exe?
Community
Member reviews and reports for this exact file hash.