Our call: Is VigiHunt_Setup.exe safe?Suspicious
- 2 high-confidence signature or behavior rules matched this file.Derived · Signature and behavior rules
- 0 of 75 antivirus engines flagged the file.Observed · Antivirus analysis
- The file has a valid code signature from viginet private limited.Observed · Code-signing metadata
ac7125f354539779d4…7ec9d45116Recommended 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.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
Complete4 signature or behavior rules matched.
External intel
Complete3 of 3 independent reference sources completed.
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
VigiHunt_Setup.exe
ac7125f354539779d447e845241bce0b816e612901260a244732ab7ec9d45116
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
C:\Windows\system32\services.exe
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\1780840486520-784110545-VigiHunt_Setup.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
1780840486520-784110545-VigiHunt_Setup.tmp
C:\Users\<USER>\AppData\Local\Temp\is-6PK90FLVF4.tmp\1780840486520-784110545-VigiHunt_Setup.tmp
04Isolated runtime analysis - Written fileObserved
_setup64.tmp
C:\Users\<USER>\AppData\Local\Temp\is-2K00F48N4Z.tmp\_isetup\_setup64.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
54.87.55.165
Contact observed during runtime.
06Isolated runtime analysis
6 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
2 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
0 of 75 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The file has a valid code signature from viginet private limited.
ProvenanceObservedSourceCode-signing metadataObserved at - 04
Scanned file: VigiHunt_Setup.exe — ac7125f354539779d447e845241bce0b816e612901260a244732ab7ec9d45116
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — C:\Windows\system32\services.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\<USER>\Desktop\1780840486520-784110545-VigiHunt_Setup.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: 1780840486520-784110545-VigiHunt_Setup.tmp — C:\Users\<USER>\AppData\Local\Temp\is-6PK90FLVF4.tmp\1780840486520-784110545-VigiHunt_Setup.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: _setup64.tmp — C:\Users\<USER>\AppData\Local\Temp\is-2K00F48N4Z.tmp\_isetup\_setup64.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 54.87.55.165 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
No saved analyst narrative
This report keeps the verified scan facts available below without inventing an analysis that was not saved with the scan.
Behavior
Plain-English impact first, then the observed runtime evidence.
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: 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.
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.
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.
- 54.87.55.165
- C:\Users\<USER>\AppData\Local\Temp\is-6PK90FLVF4.tmp\1780840486520-784110545-VigiHunt_Setup.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-2K00F48N4Z.tmp\_isetup\_setup64.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-2K00F48N4Z.tmp\_isetup\_isdecmp.dll
- C:\Users\<USER>\AppData\Local\Microsoft\Windows\Explorer\iconcache_idx.db
- C:\Users\<USER>\AppData\Local\Microsoft\Windows\Explorer\iconcache_256.db
- C:\Program Files\VigiHunt\is-44AU6O8USX.tmp
- C:\Program Files\VigiHunt\is-HAMWN9ZWQD.tmp
- C:\Program Files\VigiHunt\is-MCI8DOZGH7.tmp
- C:\Program Files\VigiHunt\is-70WHGD4Q8N.tmp
- C:\Program Files\VigiHunt\is-7L2MIRDYZE.tmp
- cversions.3.m
- Global\PythonTraceOutputMutex
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 7461a15657c7516237b0…63a825Never scannednever seen before
- cd2f60075064dfc2e65c…356b08Never scannednever seen before
- da3f122d19f811a0ee68…fde700Never scannednever seen before
- d73fd5078c34b3f4eb35…b90d22Never scannednever seen before
- 96ad1146eb96877eab59…87dcf7Never scannednever seen before
- c8ec6429d243aef1f789…676005Never scannednever seen before
- c1fb92c780b69e2cb1f1…3b9529Never scannednever seen before
- 81940e12ae3bc4e1caf9…358514Never scannednever seen before
- 9cfb1d4bfba7708b2885…cfa05eNever scannednever seen before
- 2758b9e3112a264f6da0…513d77Never scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
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.
Sample spawned PowerShell with a hidden window AND execution-policy bypass / inline command. Not definitive — legit Intune/SCCM scripts do this too — but combined with other signals it reinforces the loader profile.
Evidence"powershell.exe" -ExecutionPolicy Bypass -WindowStyle Hidden -Command "Add-MpPreference -ExclusionPath 'C:\Program Files\VigiHunt'"Sample disabled Windows Defender real-time protection or added an AV exclusion path. This is the blow-the-doors-off move malware makes right before dropping a second-stage payload.
Evidence"powershell.exe" -ExecutionPolicy Bypass -WindowStyle Hidden -Command "Add-MpPreference -ExclusionPath 'C:\Program Files\VigiHunt'"MITRE T1055 (Process Injection) observed — CreateRemoteThread / APC / reflective-DLL injection. The payload is being smuggled into a legitimate process to bypass AV hooks.
EvidenceC:\Windows\Explorer.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.
Evidence54.87.55.165
0 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
Barely seen in the wild and first surfaced recently. That limits reputation evidence, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- VigiHunt_Setup.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: viginet private limited
- Size
- 108.5 MB
- Last analyzed
- Jun 13, 2026, 3:00 PM UTC
ac7125f354539779d447e845241bce0b816e612901260a244732ab7ec9d45116Safety & 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.
Don't install it unless you're certain it came from a source you trust.
Check where you got it — an unexpected attachment or a random download link is a red flag.
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.
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.