Is AxGlyph_Setup_Win_en.exe safe?
Three tier-1 detections, a revoked certificate, and observed injection, LSASS access, defense evasion, and destructive-technique mappings warrant strict caution.
Nine of 75 engines flagged this installer, including three tier-1 detections, but they do not strongly agree on a named family. Runtime evidence mapped process injection, LSASS targeting, defense evasion, and destructive techniques, while its publisher certificate lacks verification and is tagged as revoked. Avoid running it unless the vendor can independently authenticate this exact hash.
29398f4e31b244045d…3e1c3d87ade7f3Recommended next actions
Before installing
Do not install it until the source and publisher can be verified independently.
If you already installed it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Download a fresh installer 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.
Nine of 75 engines flagged this installer, including three tier-1 detections, but they do not strongly agree on a named family. Runtime evidence mapped process injection, LSASS targeting, defense evasion, and destructive techniques, while its publisher certificate lacks verification and is tagged as revoked. Avoid running it unless the vendor can independently authenticate this exact hash.
The installer drew 9 of 75 detections, including three independent tier-1 votes, which prevents treating the findings as low-trust noise. The labels are inconsistent and lack strong family consensus, so they do not establish one specific malware family. A completed sandbox recorded T1055 and other offensive mappings, plus LSASS-targeting activity, although it issued no explicit malicious judgment. The Keroro Software LLC signature is not verified in the evidence, has no trusted-publisher or historical support, and the file carries a revoked-certificate tag. Ten dropped files produced no confirmed malicious child, and researcher intelligence supplied no corroborating hit. Network reputation is inconclusive because only one host was inspected despite multiple observed IP and URL contacts.
What We Detected
Nine of 75 antivirus engines flagged the installer. Three tier-1 engines contributed independent malicious votes, with GData naming Trojan.Agent and Avast/AVG using the reputation-based FileRepMalware label; however, the engines did not reach strong agreement on a single family.
Threat Behavior
The completed sandbox mapped five offensive techniques: T1055 process injection, T1485 data destruction, T1486 data encryption for impact, T1548 privilege escalation, and T1562.001 impairment of defenses. Saved heuristic evidence also indicates access targeting LSASS, which is associated with credential theft. These mappings are concerning but do not prove every technique was successfully executed, and the sandbox itself supplied no explicit malicious judgment.
The sample contacted nine IP addresses and one URL. Only one host received a saved reputation inspection, so no complete host-reputation conclusion is available. Ten dropped children were inspected without a confirmed malicious result, but all remain unclassified.
What To Do Now
Do not execute the installer on a production system. Keep endpoint protection enabled, obtain a fresh installer from the publisher's official release channel, and verify both its digital signature and SHA-256 hash with the publisher before use. If it already ran, isolate the device and perform a full endpoint scan, with particular attention to credential access and unexpected encryption or security-setting changes.
Where this verdict could be wrong5 caveats
- 13 tier-1 engines reported no detection, including BitDefender, ESET-NOD32, Kaspersky, and Fortinet.
- behaviour.hasMaliciousSandboxVerdict=false, so the completed sandbox did not issue an explicit malware judgment despite the concerning techniques.
- droppedChildren.hasMaliciousChild=false, although all 10 inspected children remain unclassified rather than affirmatively clean.
- externalIntel.yaraify.ruleCount=0, externalIntel.circl.hit=false, and externalIntel.malwareBazaar.hit=false provide no researcher-intelligence corroboration.
- peAnalysis.highEntropyCode=false and peAnalysis.likelyPacked=false show no static packing indicator.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 13 tier-1 engines reported no detection
- behaviour.hasMaliciousSandboxVerdict=false
- droppedChildren.hasMaliciousChild=false
- externalIntel.yaraify.ruleCount=0 and externalIntel.circl.hit=false
- peAnalysis.likelyPacked=false and peAnalysis.highEntropyCode=false
- 9/75 antivirus detections, including tier1Malicious=3
- Observed T1055 process-injection mapping
- LSASS-targeting evidence in MalwareTips.Synth.CredentialDumper
- T1485 and T1486 destructive-impact mappings
- T1562.001 defense-impairment mapping
- Revoked-certificate tag with signing.verified=null
Quarantine the file and obtain a newly signed copy through the publisher's official channel. Keep endpoint protection enabled; if this copy already ran, isolate and scan the system before entering sensitive credentials.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete9 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 of 10 contacted hosts were cross-checked; coverage is incomplete.
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
- 25MITRE ATT&CK techniques
- 15spawned processes
- 10network contacts
- 31filesystem & 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: Encrypted files or data, behaviour commonly associated with ransomware.
High concern: Changed an auto-start location that can make code run after sign-in or restart.
High concern: Attempted to impair or bypass security controls.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
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
AxGlyph_Setup_Win_en.exe
29398f4e31b244045dedef5fdd56f2f926507619170525049c3e1c3d87ade7f3
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\AxGlyph_Setup_Win_en.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
taskkill /F /IM AxSnap.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
nscC351.tmp
C:\Users\<USER>\AppData\Local\Temp\nscC351.tmp
04Isolated runtime analysis - Written fileObserved
LangDLL.dll
C:\Users\<USER>\AppData\Local\Temp\nshC371.tmp\LangDLL.dll
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
121.199.3.143
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
13.107.246.38
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 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.
- 121.199.3.143
- 13.107.246.38
- 150.171.73.13
- 47.76.188.115
- 151.101.128.176
- 13.107.213.38
- 64.233.160.132
- 150.171.74.13
- 162.159.36.2
- http://www.axmath.cn:3310/G@20250713==
- C:\Users\<USER>\AppData\Local\Temp\nscC351.tmp
- C:\Users\<USER>\AppData\Local\Temp\nshC371.tmp\LangDLL.dll
- C:\Users\<USER>\AppData\Local\Temp\nshC371.tmp\ioSpecial.ini
- C:\Users\<USER>\AppData\Local\Temp\nshC371.tmp\modern-wizard.bmp
- C:\Users\<USER>\AppData\Local\Temp\nshC371.tmp\modern-header.bmp
- C:\Users\<USER>\AppData\Local\Temp\nshC371.tmp\AccessControl.dll
- C:\Users\<USER>\AppData\Local\Temp\nshC371.tmp\InstallOptions.dll
- C:\Users\<USER>\AppData\Local\Temp\nshC371.tmp\ioSpecial.ini
- C:\Users\<USER>\AppData\Local\Temp\nshC371.tmp\LangDLL.dll
- C:\Users\<USER>\AppData\Local\Temp\nshC371.tmp\modern-header.bmp
- cversions.3.m
- Global\OneSettingQueryMutex+compat+encapsulation
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- c52a8c79c8e1d28c751e…36acdeNever scannednever seen before
- a4f1467ea1ae546fd24a…a42d6aNever scannednever seen before
- 82f20d5646316f83b927…4c67dbNever scannednever seen before
- 6c50fcf1ae20a33a1d74…2f77fbNever scannednever seen before
- da7b0dfc24faa6b991cc…35977dNever scannednever seen before
- 32d55c46c9ca7629f99b…ae743aNever scannednever seen before
- f6a5021fccb2d23b4c93…0120deNever scannednever seen before
- 5520e7a201f22e156e64…28afaeNever scannednever seen before
- a314216833b97642b310…82a132Never scannednever seen before
- 88e44bc7f2866c59b645…ad77b3Never scannednever seen before
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
- 9 / 75engines flagged
- 3sources 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
9 of 75 antivirus engines flagged the file, including Avast and AVG.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 4 times from 3 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: AxGlyph_Setup_Win_en.exe — 29398f4e31b244045dedef5fdd56f2f926507619170525049c3e1c3d87ade7f3
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\AxGlyph_Setup_Win_en.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — taskkill /F /IM AxSnap.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: nscC351.tmp — C:\Users\<USER>\AppData\Local\Temp\nscC351.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: LangDLL.dll — C:\Users\<USER>\AppData\Local\Temp\nshC371.tmp\LangDLL.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 121.199.3.143 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 13.107.246.38 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: generic-trojan
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\Explorer.EXESandbox 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.
Evidence121.199.3.143 · 13.107.246.38 · 150.171.73.13
9 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
Rarely uploaded, but has been around for a while. Often niche legitimate software or old internal tooling; not a strong malware signal on its own.
Fingerprint and provenance
- File name
- AxGlyph_Setup_Win_en.exe
- Format
- Win32 EXE
- Code signing
- Signature not verified: Keroro Software LLC
- Size
- 14.2 MB
- Last analyzed
- Sep 19, 2026, 4:06 PM UTC
29398f4e31b244045dedef5fdd56f2f926507619170525049c3e1c3d87ade7f3Safety & 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 install 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. Download a fresh installer 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 AxGlyph_Setup_Win_en.exe safe, or is it malware?
What is AxGlyph_Setup_Win_en.exe?
How many antivirus engines detected AxGlyph_Setup_Win_en.exe?
What should I do if I already installed AxGlyph_Setup_Win_en.exe?
How do I remove AxGlyph_Setup_Win_en.exe?
What kind of malware is AxGlyph_Setup_Win_en.exe?
Is AxGlyph_Setup_Win_en.exe digitally signed?
What is the SHA-256 hash of AxGlyph_Setup_Win_en.exe?
How up to date is this analysis of AxGlyph_Setup_Win_en.exe?
Community
Member reviews and reports for this exact file hash.