Is GPO-Hubv2.0.0.exe safe?
Limited generic detections conflict with concerning runtime indicators involving process injection, LSASS access, and direct-IP traffic from an unsigned executable.
Only 3 of 74 engines flagged the file, with no tier-1 detections or agreed malware family. However, the completed sandbox run produced indicators associated with process injection and LSASS access, and the executable is unsigned, so it should not be run without further verification.
753dc22f583efa21e7…419ce21b4ba358Recommended 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.
Only 3 of 74 engines flagged the file, with no tier-1 detections or agreed malware family. However, the completed sandbox run produced indicators associated with process injection and LSASS access, and the executable is unsigned, so it should not be run without further verification.
Three of 74 engines raised generic alerts, including one tier-2 detection, but no tier-1 engine identified malware or established a family consensus. The completed sandbox observation nevertheless mapped activity to T1055 and T1486, with an additional heuristic recording access directed at LSASS. Two IP addresses were contacted directly, but no complete host-reputation result is available because that cross-check was not saved. The executable is unsigned and has no publisher history, reducing confidence in its provenance. Conversely, no sandbox produced an explicit malware judgment, no inspected child was identified as malicious, and the file has substantial historical prevalence. These mixed findings support isolation and source verification rather than immediate execution.
What We Detected
Three of 74 antivirus engines flagged the executable. CrowdStrike supplied a generic high-confidence machine-learning detection, while APEX and Bkav supplied generic malware labels; no tier-1 engine flagged it and no named family consensus emerged.
Threat Behavior
One completed sandbox run mapped activity to T1055 and T1486, and a separate heuristic recorded process activity targeting LSASS. The sample also contacted 185.199.110.133 and 162.159.36.2 directly. No complete reputation cross-check is available for those addresses, so their risk cannot be resolved from the saved evidence. No explicit malware sandbox judgment or known malicious child was recorded, although the ten inspected children remain individually unclassified.
What To Do Now
Keep the file quarantined and do not grant it administrator privileges. Verify its SHA-256 hash and download source against an official release channel, or obtain a publisher-signed build before considering execution; keep endpoint protection enabled.
Where this verdict could be wrong4 caveats
- No tier-1 engine flagged the sample, and 11 tier-1 engines reported it undetected.
- behaviour.hasMaliciousSandboxVerdict=false, and droppedChildren.hasMaliciousChild=false after 10 children were inspected, although all ten child verdicts remain unknown.
- prevalence records 139 sources and 153 submissions over 209 days, which is less consistent with a newly distributed threat.
- externalIntel.yaraify.ruleCount=0, externalIntel.circl.hit=false, and externalIntel.malwareBazaar.hit=false; these absences may reflect coverage limitations rather than proof of benignity.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- No tier-1 malicious detections or family consensus
- 11 tier-1 engines reported the file undetected
- No explicit malicious sandbox judgment
- No malicious child identified among 10 inspected children
- Observed across 139 sources and 153 submissions over 209 days
- Unsigned Win32 executable with no established signer history
- Sandbox indicator for process injection technique T1055
- Heuristic evidence of activity targeting LSASS
- Runtime mapping to T1486
- Direct connections to two IP addresses without a completed reputation cross-check
- Three generic antivirus detections, including CrowdStrike at tier2
Quarantine the executable until its publisher and official distribution channel can be verified. If validation is impossible, avoid running 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
Complete3 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
- 12spawned processes
- 2network contacts
- 17filesystem & 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.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Removed execution artefacts or logs, which can conceal activity.
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
GPO-Hubv2.0.0.exe
753dc22f583efa21e7b8aa251880d681b1ed1408887cea1501419ce21b4ba358
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\program.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\cmd.exe /c "ver"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
_avif.cp312-win_amd64.pyd
C:\Users\<USER>\AppData\Local\Temp\_MEI10042\PIL\_avif.cp312-win_amd64.pyd
04Isolated runtime analysis - Written fileObserved
_imaging.cp312-win_amd64.pyd
C:\Users\<USER>\AppData\Local\Temp\_MEI10042\PIL\_imaging.cp312-win_amd64.pyd
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
185.199.110.133
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
162.159.36.2
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.
- 185.199.110.133
- 162.159.36.2
- C:\Users\<USER>\AppData\Local\Temp\_MEI10042\PIL\_avif.cp312-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI10042\PIL\_imaging.cp312-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI10042\PIL\_imagingcms.cp312-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI10042\PIL\_imagingft.cp312-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI10042\PIL\_imagingmath.cp312-win_amd64.pyd
- PreIndexedSourceCPL_Microsoft.Winget.Source_8wekyb3d8bbwe
- 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.
- 48f4a239c25354f0e9f8…17ecedNever scannednever seen before
- 3271d39d7b4dcd841e8e…efe5e5Never scannednever seen before
- cb71909bf01a3a7a4c73…d46e13Never scannednever seen before
- 6a99bc0128e0c7d6cbbf…cbc6c8Never scannednever seen before
- 98074c85650a420a095a…b084e9Never scannednever seen before
- 384511bf1b596689acd4…48d180Never scannednever seen before
- 49949fa3de20481915af…96eb34Never scannednever seen before
- 81eca6840b87f2def9fc…d7aaaaNever scannednever seen before
- 4f05f31ca026bbfeeee4…7ab5deNever scannednever seen before
- 3130bf26da0c840c1e02…5a3539Never 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
- 3 / 74engines flagged
- 139sources 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
3 of 74 antivirus engines flagged the file, including APEX and Bkav.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has a long, established submission history across 139 sources.
ProvenanceDerivedSourceSubmission historyObserved at - 04
Scanned file: GPO-Hubv2.0.0.exe — 753dc22f583efa21e7b8aa251880d681b1ed1408887cea1501419ce21b4ba358
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\program.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\cmd.exe /c "ver"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: _avif.cp312-win_amd64.pyd — C:\Users\<USER>\AppData\Local\Temp\_MEI10042\PIL\_avif.cp312-win_amd64.pyd
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: _imaging.cp312-win_amd64.pyd — C:\Users\<USER>\AppData\Local\Temp\_MEI10042\PIL\_imaging.cp312-win_amd64.pyd
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 185.199.110.133 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 162.159.36.2 — 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 LocalSystemNetworkRestricted -p -s StorSvcSandbox 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.
Evidence185.199.110.133 · 162.159.36.2
3 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
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
- GPO-Hubv2.0.0.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 53.4 MB
- Last analyzed
- Sep 17, 2026, 1:50 PM UTC
753dc22f583efa21e7b8aa251880d681b1ed1408887cea1501419ce21b4ba358Safety & 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 GPO-Hubv2.0.0.exe safe, or is it malware?
What is GPO-Hubv2.0.0.exe?
How many antivirus engines detected GPO-Hubv2.0.0.exe?
What should I do if I already ran GPO-Hubv2.0.0.exe?
How do I remove GPO-Hubv2.0.0.exe?
What is the SHA-256 hash of GPO-Hubv2.0.0.exe?
How up to date is this analysis of GPO-Hubv2.0.0.exe?
Community
Member reviews and reports for this exact file hash.