Is KAHRGUOGYU.htm safe?
No antivirus engine flagged the HTML file and sandbox behaviour shows only routine system discovery.
Zero of 75 engines detected the file. Sandbox execution recorded only ambient system-information queries and two direct-IP connections with no malicious verdict returned.
9025be1df13bfcb5d8…d726ba7ebe2f28Recommended next actions
Before opening
Open it only when you trust its source; use an isolated viewer if the origin is uncertain.
If you already opened it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
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.
Zero of 75 engines detected the file. Sandbox execution recorded only ambient system-information queries and two direct-IP connections with no malicious verdict returned.
The complete absence of malicious detections across 75 reporting engines, including 16 tier-1 engines, outweighs the single heuristic that notes direct-IP traffic. Sandbox results contain no offensive MITRE techniques and no malicious verdict. The file is brand-new and rare, but nothing in the evidence indicates malicious intent.
What We Detected
75 engines scanned the 2.4 KB HTML file; none returned a malicious or suspicious result. Sandbox execution produced one ambient technique (T1082) and wrote several Windows Error Reporting files, but no malicious verdict was issued.
Threat Behavior
The sample contacted two external IP addresses without an associated domain name. The heuristic flagged this pattern, yet the sandbox did not classify the activity as malicious and no offensive techniques were observed.
What To Do Now
Keep endpoint protection enabled. If the file originated from an unexpected source, treat it with normal caution for any newly received HTML document.
Where this verdict could be wrong1 caveat
- contactedHosts is null — no complete host-reputation result available to confirm whether the two IPs are known malicious.
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/75 engines flagged the file
- sandbox returned no malicious verdict
- rare_new prevalence (first submission today)
- direct-IP connections without domain recorded
The file can be opened with standard precautions; no security action is required based on current evidence.
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
Partial2 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete1 signature or behavior rule matched.
External intel
PartialIndependent reference checks were attempted but are incomplete.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 1MITRE ATT&CK techniques
- 2spawned processes
- 2network contacts
- 5filesystem & mutex artifacts
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
KAHRGUOGYU.htm
9025be1df13bfcb5d88bb105de92837082d24c55b42be64aabd726ba7ebe2f28
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" "C:\Users\<USER>\Desktop\document.html"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\WerFault.exe -u -p 2804 -s 3872
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Temp
C:\ProgramData\Microsoft\Windows\WER\Temp
04Isolated runtime analysis - Written fileObserved
ad31e359-b274-4f56-ba80-312d3b6a632f
C:\ProgramData\Microsoft\Windows\WER\Temp\ad31e359-b274-4f56-ba80-312d3b6a632f
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
150.171.109.183
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
150.171.73.13
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.
- 150.171.109.183
- 150.171.73.13
- C:\ProgramData\Microsoft\Windows\WER\Temp
- C:\ProgramData\Microsoft\Windows\WER\Temp\ad31e359-b274-4f56-ba80-312d3b6a632f
- C:\ProgramData\Microsoft\Windows\WER\ReportQueue
- C:\ProgramData\Microsoft\Windows\WER\Temp\c80c4e4a-3604-4931-af34-7355a59d70f1
- C:\ProgramData\Microsoft\Windows\WER\ReportArchive
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 / 75engines flagged
- 1sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 75 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
One or more independent reference checks were incomplete or unavailable.
ProvenanceDerivedSourceExternal-intelligence coverageObserved at - 03
The hash has been submitted 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: KAHRGUOGYU.htm — 9025be1df13bfcb5d88bb105de92837082d24c55b42be64aabd726ba7ebe2f28
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" "C:\Users\<USER>\Desktop\document.html"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\WerFault.exe -u -p 2804 -s 3872
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Temp — C:\ProgramData\Microsoft\Windows\WER\Temp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: ad31e359-b274-4f56-ba80-312d3b6a632f — C:\ProgramData\Microsoft\Windows\WER\Temp\ad31e359-b274-4f56-ba80-312d3b6a632f
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 150.171.109.183 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 150.171.73.13 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
Available reference checks returned no match, but at least one source was unavailable. This is not a clean result.
Signatures and behavior heuristics
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
The 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.
Evidence150.171.109.183 · 150.171.73.13
0 of 75 engines flagged this file
View all 75 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
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
- KAHRGUOGYU.htm
- Format
- HTML
- Code signing
- Not applicable to this file type
- Size
- 2.4 KB
- Last analyzed
- Aug 21, 2026, 8:43 AM UTC
9025be1df13bfcb5d88bb105de92837082d24c55b42be64aabd726ba7ebe2f28Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Open it only when you trust its source; use an isolated viewer if the origin is uncertain.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is KAHRGUOGYU.htm safe?
What is KAHRGUOGYU.htm?
How many antivirus engines detected KAHRGUOGYU.htm?
What is the SHA-256 hash of KAHRGUOGYU.htm?
Is it safe to open KAHRGUOGYU.htm?
How up to date is this analysis of KAHRGUOGYU.htm?
Community
Member reviews and reports for this exact file hash.