Is AGHelper_x64.exe safe?
No antivirus engine detected this signed executable, but one sandbox reported malware-like activity involving possible process injection and other offensive techniques.
The file has a verified Mirillis signature and received no detections from 76 antivirus engines. However, completed runtime analysis produced a malicious assessment and mapped activity to process injection, service manipulation, and reflective code loading, so execution should be deferred until its source and signature are independently verified.
14bc1c0ba919483f96…740d03b5d44efcRecommended 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.
The file has a verified Mirillis signature and received no detections from 76 antivirus engines. However, completed runtime analysis produced a malicious assessment and mapped activity to process injection, service manipulation, and reflective code loading, so execution should be deferred until its source and signature are independently verified.
Static scanning is strongly reassuring: none of 76 engines raised a detection, and 15 tier-1 engines reported no detection. The executable is signed with a verified certificate for Mirillis Sp. z o.o., although no established publisher history is available in the evidence. Runtime analysis is the principal concern because one sandbox produced a malicious assessment and associated the sample with T1055.003, T1543.003, and T1620. Those mappings can occur in specialized legitimate software, and no malicious dropped child, known malware family, or external intelligence match corroborates them. Host-reputation coverage was incomplete because only three entries were inspected despite numerous observed domains, addresses, and a URL. The combined evidence therefore warrants caution rather than treating either the clean static scan or the sandbox result as conclusive alone.
What We Detected
The executable received 0 detections from 76 antivirus engines, including no tier-1 detections. Its code signature verifies as “Mirillis Sp. z o.o.”, no brand mismatch was detected, and static PE analysis found neither likely packing nor high-entropy code.
Threat Behavior
One completed sandbox assessment reported malware-like activity. The recorded techniques include T1055.003, T1543.003, and T1620, covering possible process injection, Windows service manipulation, and reflective code loading. The fired ProcessInjection heuristic supports concern but does not independently establish intent or the exact injection method. Three dropped files were inspected without a malicious finding, although all remain unclassified. The host cross-check did not cover every observed domain, address, and URL, so a complete network-reputation result is unavailable.
What To Do Now
Do not run the file merely because the antivirus scan is empty. Confirm that it came directly from the official Mirillis distribution channel, inspect the certificate details locally, and compare its SHA-256 hash with a vendor-published value if available. Keep endpoint protection enabled and quarantine or remove the file if its origin cannot be verified.
Where this verdict could be wrong4 caveats
- All 76 engines were free of detections, including 15 tier-1 engines reporting no detection.
- The executable has a verified 'Mirillis Sp. z o.o.' signature, no brand mismatch, and no packing indicators.
- The three inspected dropped children were not established as malicious, although each remains unclassified.
- No YARAify or MalwareBazaar match corroborates the sandbox concern.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0/76 antivirus engines detected the executable
- 15 tier-1 engines reported no detection
- Verified code signature from Mirillis Sp. z o.o.
- brandMismatch.detected was not present
- peAnalysis.likelyPacked=false and peAnalysis.highEntropyCode=false
- behaviour.hasMaliciousSandboxVerdict=true in completed runtime analysis
- Offensive technique mappings T1055.003, T1543.003, and T1620
- MalwareTips.Synth.ProcessInjection fired at high severity
- signing.signerStats.found=false, leaving the publisher without historical sample support
- All three dropped-child verdicts remain unknown
- Contacted-host reputation coverage was incomplete
Only use this executable if its download source and Mirillis signature can be independently verified against the official vendor channel. Otherwise, quarantine it and keep endpoint protection enabled.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 76 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial3 of 12 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete1 signature or behavior rule 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
- 21MITRE ATT&CK techniques
- 5spawned processes
- 13network contacts
- 20filesystem & 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: Created or modified a system service, which can keep code running.
High concern: Manipulated how the operating system loads code, which can redirect execution.
High concern: Loaded code directly into memory instead of from a normal file.
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.
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
AGHelper_x64.exe
14bc1c0ba919483f965c9f63b48867e24390390a75408ffd9a740d03b5d44efc
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\software.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
%SAMPLEPATH%\14bc1c0ba919483f965c9f63b48867e24390390a75408ffd9a740d03b5d44efc.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
WERDB47.tmp
C:\ProgramData\Microsoft\Windows\WER\Temp\WERDB47.tmp
04Isolated runtime analysis - Written fileObserved
WERDB47.tmp.dmp
C:\ProgramData\Microsoft\Windows\WER\Temp\WERDB47.tmp.dmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostDerived
res.public.onecdn.static.microsoft
Saved reputation verdict: safe.
06Contacted-host cross-check - Contacted hostDerived
www.microsoft.com
Saved reputation verdict: safe.
07Contacted-host cross-check - +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; 1 returned "malicious".
Adversary techniques mapped to the MITRE ATT&CK framework.
- res.public.onecdn.static.microsoft
- www.microsoft.com
- repository.certum.pl
- a83f:8110:106b:300:0:0:0:0
- 192.168.0.59
- 23.216.147.71
- 20.99.186.246
- 72.247.234.254
- 104.98.118.139
- 52.185.73.156
- 23.213.37.172
- 23.215.11.233
- http://repository.certum.pl/ctnca2.cer
- HKEY_USERS\S-1-5-21-575823232-3065301323-1442773979-1000\Software\Microsoft\SystemCertificates\Root\Certificates\0174E68C97DDF1E0EEEA415EA336A163D2B61AFD\Blob
- HKEY_USERS\S-1-5-21-575823232-3065301323-1442773979-1000\Software\Microsoft\Windows\Windows Error Reporting\Debug\StoreLocation
- HKEY_USERS\S-1-5-21-575823232-3065301323-1442773979-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WarnonZoneCrossing
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WarnonZoneCrossing
- \REGISTRY\A\{d879c815-17eb-3b50-e271-902f28570461}\Root\InventoryApplicationFile\PermissionsCheckTestKey
- \REGISTRY\A\{d879c815-17eb-3b50-e271-902f28570461}\Root\InventoryApplicationFile\executable.exe|83c770cda7bf1166
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERDB47.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERDB47.tmp.dmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERDC52.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERDC52.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERDD0E.tmp
- C:\Windows\System32\wbem\Performance\WmiApRpl.h
- C:\Windows\System32\wbem\Performance\WmiApRpl.ini
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERDB47.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERDB47.tmp.dmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERDC52.tmp
- \Sessions\1\BaseNamedObjects\Local\WERReportingForProcess8036
- \Sessions\1\BaseNamedObjects\Global\AmiProviderMutex_InventoryApplicationFile
- \Sessions\1\BaseNamedObjects\Global\c14ede30-ce15-4188-9ae1-2c5ee0e21288
Files this sample writes at runtime
This file drops 3 children at runtime. None are currently flagged malicious in our cache.
- b33efcb95235b98b4850…29307fNever scannednever seen before
- c82c2f4979f46c75cd8d…ba5dcfNever scannednever seen before
- c3f8dd7c41c0e061249f…5cad9eNever 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.
- 1rule hit recorded
- 0 / 76engines flagged
- 12sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 isolated runtime environment classified the observed behavior as malicious.
Verdict inputView chapterProvenanceObservedSourceIsolated runtime analysisObserved at - 02
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 03
0 of 76 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 04
Scanned file: AGHelper_x64.exe — 14bc1c0ba919483f965c9f63b48867e24390390a75408ffd9a740d03b5d44efc
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\software.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — %SAMPLEPATH%\14bc1c0ba919483f965c9f63b48867e24390390a75408ffd9a740d03b5d44efc.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: WERDB47.tmp — C:\ProgramData\Microsoft\Windows\WER\Temp\WERDB47.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: WERDB47.tmp.dmp — C:\ProgramData\Microsoft\Windows\WER\Temp\WERDB47.tmp.dmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: res.public.onecdn.static.microsoft — Saved reputation verdict: safe.
ProvenanceDerivedSourceContacted-host cross-checkObserved at - 10
Contacted host: www.microsoft.com — Saved reputation verdict: safe.
ProvenanceDerivedSourceContacted-host cross-checkObserved 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.
Evidence"C:\Users\<USER>\Desktop\software.exe"
0 of 76 engines flagged this file
View all 76 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
- AGHelper_x64.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: Mirillis Sp. z o.o.
- Size
- 204.4 KB
- Last analyzed
- Oct 6, 2026, 9:24 AM UTC
14bc1c0ba919483f965c9f63b48867e24390390a75408ffd9a740d03b5d44efcSafety & 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 AGHelper_x64.exe safe, or is it malware?
What is AGHelper_x64.exe?
How many antivirus engines detected AGHelper_x64.exe?
What should I do if I already ran AGHelper_x64.exe?
How do I remove AGHelper_x64.exe?
Is AGHelper_x64.exe digitally signed?
What is the SHA-256 hash of AGHelper_x64.exe?
How up to date is this analysis of AGHelper_x64.exe?
Community
Member reviews and reports for this exact file hash.