MalwareTips

File scan report

Scan another file

Verdict Suspicious

Analyzed , 1 month ago

Is VettingAgent_04ce77ce63fd8806e0c0df9fcd48b3b5.exe safe? Treat it as suspicious.

The antivirus detections are weak: 3 of the 65 antivirus engines that checked it flagged the file, with no major detections or family consensus.

Read the whole reasonShow less

Why Suspicious? 3 antivirus engines flag it, but no major engine agrees; nothing else confirms it.

Limited evidence · One sign points to a problem; nothing else confirms it.

Don't run it until you know where it came from

If it came from a link, an attachment or a stranger, delete it.

What to do now4 steps

Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.

What to do

  1. Don't run it unless you're sure where it came from.

  2. Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.

  3. If you can't confirm where it came from, delete it. If you need the program, download it again from the publisher's own website.

If you already ran it

  1. Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.

Not sure what to do?

Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.

Paste this report's link in your topic so helpers can see what was found.

Why we think so

Share this file report

VettingAgent_04ce77ce63fd8806e0c0df9fcd48b3b5.exe: Suspicious — MalwareTips file scan

The link always shows the latest result for this exact file (its SHA-256 fingerprint).

Reads the latest antivirus results for this file's hash. Nothing is uploaded.

Antivirus results

3 of 65 flagged

  • Flagged 3
  • No detection 62
  • No result 10
FileVettingAgent_04ce77ce63fd8806e0c0df9fcd48b3b5.exe13.2 MBSHA-256 fb7cf9dcc1b9…491a57
  • Code signing Unsigned
  • Test run Completed
  • First seen 4mo ago
3 of the 65 antivirus engines that checked it flag it, including Deep Instinct and APEX.

Chapter 02

Why we think so

6 points against it and 4 in its favour, checked against the scan evidence.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

Analyst conclusion

Three of the 65 antivirus engines that checked it raised generic detections, but none came from major antivirus engines and no malware family was identified. That detection pattern alone would not establish a malware finding. The stronger concern is evidence from the test run mapped to T1055, T1485, T1486, and T1562.001, plus activity targeting the Windows password store. The executable is unsigned and has no established publisher history to explain those capabilities. Counter-signals include 14 major antivirus engines reporting no detection, no explicit malicious sandbox verdict, and no identified malicious child, leaving the evidence mixed rather than conclusive.

Where this verdict could be wrong3 caveats
  • No sandbox returned a malicious verdict, and no dropped file is known to be malicious across 10 inspected children, although every child remained unclassified.
  • No community YARA rule matched, the hash is not in the known-software reference database, and the hash is not listed in the MalwareBazaar malware database; 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.

6 sources checked · 5 complete · 1 partial. See every source

Chapter 03

What it did in our test

It ran in our isolated test environment; no test environment rated what it did as risky.

Test run summary

Capture complete
  • 31sandbox rule tags
  • 8spawned processes
  • 12network contacts
  • 16filesystem & mutex artifacts

What the test run showed

What the file did on a test computer

Confirmed in the test run

  • Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).

  • Moderate concern: Ran commands or a script on the test computer.

  • Moderate concern: Used an unusual way to talk to a server.

  • Moderate concern: Downloaded a file during the test run.

  • Moderate concern: Checked whether it was running on a test computer.

  • Moderate concern: Hid files or windows on the test computer.

  • Note: Read the user name of the test computer.

Sandbox labels we could not confirm (common in safe files too)

  • Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.

  • Not confirmed: Showed activity a sandbox rule links to file encryption; no ransomware behaviour was confirmed.

  • Not confirmed: A sandbox rule tagged this run as weakening security settings; no setting change was recorded.

  • Not confirmed: A sandbox rule tagged this run as changing how Windows loads code; nothing confirms it.

This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.

Recorded behavior

What happened in the test

Grouped by step. The order is not a timeline.

Seen in the test runWorked out from other results

  1. Input file

    The submitted object

    1
    1. Evidence 1 of 7: FileSeen in the test run

      VettingAgent_04ce77ce63fd8806e0c0df9fcd48b3b5.exe

      fb7cf9dcc1b9b45e81abab48b47abe8e89bd5fb8696f614192368df1d5491a57

      Uploaded file

  2. Processes

    What ran

    2
    1. Evidence 2 of 7: ProcessSeen in the test run

      powershell

      powershell -NoProfile -NonInteractive -Command "Get-PnpDevice -Class Camera -ErrorAction SilentlyContinue | Where-Object {$_.Status -eq 'OK'} | Select-Object -ExpandProperty FriendlyName"

      Test run
    2. Evidence 3 of 7: ProcessSeen in the test run

      VettingAgent_2b47f5f846c94f2bdda7baaa4c3d1606.exe

      "C:\Users\<USER>\Desktop\VettingAgent_2b47f5f846c94f2bdda7baaa4c3d1606.exe"

      Test run
    3. +1 more recorded observation

  3. Files

    Created or changed

    2
    1. Evidence 4 of 7: Written fileSeen in the test run

      StartupProfileData-NonInteractive

      C:\Users\<USER>\AppData\Local\Microsoft\Windows\PowerShell\StartupProfileData-NonInteractive

      Test run
    2. Evidence 5 of 7: Written fileSeen in the test run

      mfc140u.dll

      C:\Users\<USER>\AppData\Local\Temp\_MEI59202\Pythonwin\mfc140u.dll

      Test run
    3. +1 more recorded observation

  4. Network

    Hosts contacted

    2
    1. Evidence 6 of 7: Contacted hostSeen in the test run

      172.67.193.73

      Contacted during the test run.

      Test run
    2. Evidence 7 of 7: Contacted hostSeen in the test run

      104.17.147.22

      Contacted during the test run.

      Test run
    3. +1 more recorded observation

7 facts from the test run. See the full activity list.

Chapter 04

Technical details

3 of the 65 antivirus engines that checked it flag it; no publisher signature.

Sources checked

Every check behind this verdict

6 sources checked · 5 complete · 1 partial. Complete means the check returned a usable result; it does not mean the file is safe.

SourceStatusResultChecked
Antivirus enginesVirusTotal · 75 enginesCompleteRisk signal: 3 of 65 engines flagged it · 10 gave no result Details for antivirus engines
Sandbox runVirusTotal sandboxesCompleteRuntime behaviour was recorded Details for sandbox run
Contacted hostsMalwareTips URL scannerPartial5 of 12 contacted hosts were cross-checked; coverage is incomplete Details for contacted hosts
Signature rulesYARAify community rules + MalwareTips rulesComplete1 MalwareTips behaviour rule Details for signature rules
Malware sample databaseabuse.ch MalwareBazaarCompleteNot listed
Known-software referenceCIRCL hashlookupCompleteNo match

Engines that flagged it 3

  • APEXMalicious
  • BkavW32.Malware.CFCC61D1
  • DeepInstinctMALICIOUS

File fingerprint

Last analyzed
Sep 8, 2026, 3:58 PM UTC
SHA-256
fb7cf9dcc1b9b45e81abab48b47abe8e89bd5fb8696f614192368df1d5491a57
SHA-1
b48aa3b058a6ce8395bedcc5d85309d7145a0763
MD5
bef89bee272a069107894177af2edf69

About this file

VettingAgent_04ce77ce63fd8806e0c0df9fcd48b3b5.exe is a Win32 EXE file of 13.2 MB.

Type and size
Win32 EXE · 13.2 MB
Signer
UnsignedNo code signature.
First seen
Jun 22, 2026On VirusTotal.
Submitted by
20 distinct sources
Packer
None detected
Entropy
8.00 of 8

First scanned

Chapter 05

Questions & answers

Short answers to the 6 questions people ask most about this file.

Is VettingAgent_04ce77ce63fd8806e0c0df9fcd48b3b5.exe safe, or is it malware?
VettingAgent_04ce77ce63fd8806e0c0df9fcd48b3b5.exe is rated Suspicious: some signs point to a problem, but nothing confirms it is harmful. 3 of the 65 antivirus engines that checked it flag it. Don't run it unless you're sure where it came from. If you need the program, download it again from the publisher's own website.
What is VettingAgent_04ce77ce63fd8806e0c0df9fcd48b3b5.exe?
VettingAgent_04ce77ce63fd8806e0c0df9fcd48b3b5.exe is a Windows program, about 13.2 MB. It carries no version information saying what it is or who made it. VirusTotal first saw it on Jun 22, 2026.
How many antivirus engines detected VettingAgent_04ce77ce63fd8806e0c0df9fcd48b3b5.exe?
3 of the 65 antivirus engines that checked it flag VettingAgent_04ce77ce63fd8806e0c0df9fcd48b3b5.exe, including Deep Instinct and APEX. We weigh which engines flagged it and what else the scan found, not just the count.
What should I do if I already ran VettingAgent_04ce77ce63fd8806e0c0df9fcd48b3b5.exe?
No infection is confirmed: the rating is a caution, not a malware finding. 1) Check where it came from. If you can't confirm the source, delete it. 2) Run a full scan with your security software. 3) If the scan finds something, follow its removal steps and change passwords you typed on the device since then.
What is the SHA-256 hash of VettingAgent_04ce77ce63fd8806e0c0df9fcd48b3b5.exe?
The SHA-256 fingerprint of VettingAgent_04ce77ce63fd8806e0c0df9fcd48b3b5.exe is fb7cf9dcc1b9b45e81abab48b47abe8e89bd5fb8696f614192368df1d5491a57, and its MD5 is bef89bee272a069107894177af2edf69. Two files with the same SHA-256 are identical, so use it to check you have exactly this file, not just one with the same name.
How up to date is this analysis of VettingAgent_04ce77ce63fd8806e0c0df9fcd48b3b5.exe?
This report reflects the scan on Sep 8, 2026. A file's fingerprint never changes, but antivirus engines keep learning, so a rating can change later. To get a newer result, scan the file again: we refresh the antivirus results when the saved ones are out of date.
Chapter 06

Community

Member reviews and reports for this exact file hash.

Related file reports

Recent reports on other files with the same rating.

All file reports
Scan another
Check a different file
URL instead?
Check if a link is safe
This report and its SHA-256 fingerprint are public, so the next person who checks the same file gets an instant answer; documents and images are listed by type instead of their file name. A file we had not seen before is uploaded to VirusTotal, whose security partners and subscribers can download it; MalwareTips deletes its own copy after the scan. If you ran this file and are worried, scan your device with up-to-date security software.