Is VettingAgent_04ce77ce63fd8806e0c0df9fcd48b3b5.exe safe?
Only 3 of 75 engines flagged this unsigned executable, but its runtime evidence includes process injection, LSASS targeting, defense evasion, and destructive-technique mappings.
The antivirus detections are weak: 3 of 75 engines flagged the file, with no tier-1 detections or family consensus. However, one runtime analysis recorded process-injection and LSASS-targeting indicators alongside defense-evasion and destructive-technique mappings, so the file should not be executed on a normal system.
fb7cf9dcc1b9b45e81…368df1d5491a57Recommended 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 antivirus detections are weak: 3 of 75 engines flagged the file, with no tier-1 detections or family consensus. However, one runtime analysis recorded process-injection and LSASS-targeting indicators alongside defense-evasion and destructive-technique mappings, so the file should not be executed on a normal system.
Three of 75 engines raised generic detections, but none came from tier-1 engines and no malware family was identified. That detection pattern alone would not establish a malware finding. The stronger concern is runtime evidence mapped to T1055, T1485, T1486, and T1562.001, plus activity targeting LSASS. The executable is unsigned and has no established publisher history to explain those capabilities. Counter-signals include 14 tier-1 engines reporting no detection, no explicit malicious sandbox verdict, and no identified malicious child, leaving the evidence mixed rather than conclusive.
What We Detected
Three of 75 antivirus engines flagged the executable. APEX and Bkav are low-trust detections, while DeepInstinct is tier2; no tier-1 engine detected it and no family consensus exists. The executable is unsigned and has no publisher history.
Threat Behavior
One completed runtime analysis mapped activity to T1055 process injection, T1485 data destruction, T1486 data encrypted for impact, and T1562.001 impairment of defenses. Saved evidence also indicates activity targeting LSASS, which is associated with credential access. No sandbox supplied an explicit malicious verdict, and none of 10 inspected dropped files was identified as malicious, although all 10 children remained unclassified. Host-reputation checking covered only 5 hosts despite eight contacted IPs and additional URL hosts, so no complete network-reputation result is available.
What To Do Now
Do not run this file on a production or personal Windows system unless its origin and purpose can be independently verified. Keep endpoint protection enabled, obtain the executable from a trusted publisher channel, and isolate any system where it has already run while reviewing credential-access and defense-tampering alerts.
Where this verdict could be wrong4 caveats
- Fourteen tier-1 engines reported no detection, including BitDefender, ESET-NOD32, Kaspersky, and Fortinet; no tier-1 engine flagged the sample.
- behaviour.hasMaliciousSandboxVerdict=false, and droppedChildren.hasMaliciousChild=false across 10 inspected children, although every child remained unclassified.
- externalIntel.yaraify.ruleCount=0, externalIntel.circl.hit=false, and externalIntel.malwareBazaar.hit=false; these absences may reflect intelligence coverage limits.
- contactedHosts found no cached malicious or suspicious entries among 5 inspected hosts, but this did not cover every observed network contact.
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 engine detections among 75 total engines
- Fourteen tier-1 engines reported no detection
- No explicit malicious sandbox verdict
- No identified malicious child among 10 inspected
- No CIRCL, MalwareBazaar, or YARAify hit
- Runtime mapping to process injection (T1055)
- Saved evidence indicates LSASS-targeting activity
- Runtime mappings include T1485 and T1486
- Defense-evasion mapping T1562.001
- Unsigned Win32 executable with no signer history
- Incomplete reputation coverage for observed network contacts
Quarantine the file and verify its source and intended function before use. If it has already executed, keep protection enabled and investigate the host for LSASS access, process injection, defense tampering, and unexpected file changes.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete3 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial5 of 13 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
- 31MITRE ATT&CK techniques
- 15spawned processes
- 28network contacts
- 16filesystem & 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: Attempted to impair or bypass security controls.
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: Runs hidden system commands (script or shell).
Moderate concern: Removed execution artefacts or logs, which can conceal activity.
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
VettingAgent_04ce77ce63fd8806e0c0df9fcd48b3b5.exe
fb7cf9dcc1b9b45e81abab48b47abe8e89bd5fb8696f614192368df1d5491a57
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
powershell -NoProfile -NonInteractive -Command "Get-PnpDevice -Class Camera -ErrorAction SilentlyContinue | Where-Object {$_.Status -eq 'OK'} | Select-Object -ExpandProperty FriendlyName"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\VettingAgent_2b47f5f846c94f2bdda7baaa4c3d1606.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
StartupProfileData-NonInteractive
C:\Users\<USER>\AppData\Local\Microsoft\Windows\PowerShell\StartupProfileData-NonInteractive
04Isolated runtime analysis - Written fileObserved
mfc140u.dll
C:\Users\<USER>\AppData\Local\Temp\_MEI59202\Pythonwin\mfc140u.dll
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
172.67.193.73
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
104.17.147.22
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.
- 172.67.193.73
- 104.17.147.22
- 69.55.220.26
- 76.191.75.242
- 162.255.109.2
- 209.216.162.10
- 173.241.160.38
- 162.159.36.2
- http://speedtest1-lagrorxb.as20055.net:8080/speedtest/latency.txt?x=1782155380812
- http://speedtest5.wtechlink.com:8080/speedtest/latency.txt?x=1782155380921
- http://speedtest.desertwinds.net:8080/speedtest/latency.txt?x=1782155380999
- http://myspeed.gorge.net:8080/speedtest/latency.txt?x=1782155381093
- http://sn-speedtest-03.sandynet.org:8080/speedtest/latency.txt?x=1782155381218
- http://sn-speedtest-03.sandynet.org:8080/speedtest/random350x350.jpg?x=1782155381312.1
- C:\Users\<USER>\AppData\Local\Microsoft\Windows\PowerShell\StartupProfileData-NonInteractive
- C:\Users\<USER>\AppData\Local\Temp\_MEI59202\Pythonwin\mfc140u.dll
- C:\Users\<USER>\AppData\Local\Temp\_MEI59202\Pythonwin\win32ui.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI59202\VCRUNTIME140.dll
- C:\Users\<USER>\AppData\Local\Temp\_MEI59202\VCRUNTIME140_1.dll
- 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.
- 3f81a149ba3862776af3…ff954dNever scannednever seen before
- 96ad1146eb96877eab59…87dcf7Never scannednever seen before
- c8442f4d6d56aa28c3d4…f24e31Never scannednever seen before
- 74e0e8384f6c2503215f…530bc1Never scannednever seen before
- b1b3fd40ab437a43c8db…930c59Never scannednever seen before
- 241ef029164f9a32948e…57309dNever scannednever seen before
- eff52743773eb550fcc6…7b280aNever scannednever seen before
- 2e1f090aba941b9d2d50…aaac2fNever scannednever seen before
- 411d6f538bdbaf60f1a1…742019Never scannednever seen before
- 97b7258c32a555170e65…a08f8aNever 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 / 75engines flagged
- 20sources 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 75 antivirus engines flagged the file, including APEX and Bkav.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 21 times from 20 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: VettingAgent_04ce77ce63fd8806e0c0df9fcd48b3b5.exe — fb7cf9dcc1b9b45e81abab48b47abe8e89bd5fb8696f614192368df1d5491a57
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — powershell -NoProfile -NonInteractive -Command "Get-PnpDevice -Class Camera -ErrorAction SilentlyContinue | Where-Object {$_.Status -eq 'OK'} | Select-Object -ExpandProperty FriendlyName"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\<USER>\Desktop\VettingAgent_2b47f5f846c94f2bdda7baaa4c3d1606.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: StartupProfileData-NonInteractive — C:\Users\<USER>\AppData\Local\Microsoft\Windows\PowerShell\StartupProfileData-NonInteractive
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: mfc140u.dll — C:\Users\<USER>\AppData\Local\Temp\_MEI59202\Pythonwin\mfc140u.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 172.67.193.73 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 104.17.147.22 — 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.
Evidence172.67.193.73 · 104.17.147.22 · 69.55.220.26
3 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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- VettingAgent_04ce77ce63fd8806e0c0df9fcd48b3b5.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 12.6 MB
- Last analyzed
- Sep 8, 2026, 3:58 PM UTC
fb7cf9dcc1b9b45e81abab48b47abe8e89bd5fb8696f614192368df1d5491a57Safety & 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 VettingAgent_04ce77ce63fd8806e0c0df9fcd48b3b5.exe safe, or is it malware?
What is VettingAgent_04ce77ce63fd8806e0c0df9fcd48b3b5.exe?
How many antivirus engines detected VettingAgent_04ce77ce63fd8806e0c0df9fcd48b3b5.exe?
What should I do if I already ran VettingAgent_04ce77ce63fd8806e0c0df9fcd48b3b5.exe?
How do I remove VettingAgent_04ce77ce63fd8806e0c0df9fcd48b3b5.exe?
What is the SHA-256 hash of VettingAgent_04ce77ce63fd8806e0c0df9fcd48b3b5.exe?
How up to date is this analysis of VettingAgent_04ce77ce63fd8806e0c0df9fcd48b3b5.exe?
Community
Member reviews and reports for this exact file hash.