GridinSoft Threat Intelligence

wifihistoryview.exe file report

Under review File reputation report
MD5 3fad0905c54ea4193bf09dda3fae4b9f
Latest seen 2026-03-05 23:01:21 (2 months ago)
First seen 2024-05-11 23:00:54 (2 years ago)
Size 111 KB
Publisher NirSoft
Product WifiHistoryView

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2024-05-11 23:00:54 (2 years ago); latest analysis 2026-03-05 23:01:21 (2 months ago).

Publisher context

Company metadata: NirSoft. Product metadata: WifiHistoryView.

Observed locations

ThreatInfo has seen this file in user or system paths listed below. Unexpected locations increase the need for local verification.

Recommended action

What to do next

  1. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. Run a local scan if the file appears unexpectedly or starts with Windows.

wifihistoryview.exe is a Windows file recorded in the ThreatInfo database. It is associated with WifiHistoryView. The reported company name is NirSoft. The current detection status is Undefined, based on the latest analysis from 2026-03-05 23:01:21 (2 months ago).

ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.

Product Name: WifiHistoryView
Company Name: NirSoft
MD5: 3fad0905c54ea4193bf09dda3fae4b9f
Size: 111 KB
First Published: 2024-05-11 23:00:54 (2 years ago)
Latest Published: 2026-03-05 23:01:21 (2 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-03-05 23:01:21 (2 months ago)
%profile%\downloads\morphs_installs_april_2024-teamos\morphs_installs_april_2024-teamos\installs\ntlite\nirlauncherpackageportable.exe\nirlauncher package 1.30.11 portable
%profile%\downloads\wscc\apps
%appdata%\wscc7\apps
%sysdrive%\downloads\windows_repair_toolbox\downloads\nirlauncher
%sysdrive%\new folder

ThreatInfo has observed wifihistoryview.exe in the locations listed above. Files found in temporary folders, user profile folders, startup locations, or unusual application directories should be reviewed more carefully than files installed under a known program directory.

Windows 10 100.0%

The most common operating system signal for wifihistoryview.exe is Windows 10 with 100.0% of observed hits. If your system differs from the common profile, check whether the file was introduced by a specific installer, archive, or removable device.

wifihistoryview.exe is identified as pe for 32-bit systems. The subsystem is Windows GUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Format pe
Architecture 32-bit
Subsystem Windows GUI
Entry point 0x000104f4
Image base 0x00400000

PE Sections:

Sections 4
Raw data 112640

Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.

.text 64000 bytes · 56.8% of section data
MD5 2e85a0217ad421746951acb8cc44ac0d
.rdata 14336 bytes · 12.7% of section data
MD5 8a537bf42b0787759023985fe96d78b4
.data 1536 bytes · 1.4% of section data
MD5 68f950a3abcb06a2ec96705e9bca7b03
.rsrc 32768 bytes · 29.1% of section data
MD5 ffa90eb8d9e4c2195470d8d273455493

PE section names and hashes can reveal packing, injected resources, or unusual build artifacts. Sections with uncommon names, very large raw data, or hashes that differ from a trusted copy deserve additional review.

Report conclusion

This file is still under review

ThreatInfo has not assigned a final verdict yet. Compare the file hash, location, signature, and publisher before trusting the file on a production system.

Scan with GridinSoft Anti-Malware Use a local scan if the file origin or behavior is unclear. Check this hash on VirusTotal

Recommended next steps

  • Compare the local file MD5 with 3fad0905c54ea4193bf09dda3fae4b9f.
  • Check the file path, publisher, and signature against the details in this report.
  • Run a GridinSoft scan if the source, path, or behavior looks unusual.