GridinSoft Threat Intelligence
lib-inappbrowser.dll#4F42701C4117ECC8 file report
Why it matters
Evidence available for this file
No final classification is available yet.
First seen 2020-03-01 20:13:10 (6 years ago); latest analysis 2021-01-01 19:37:46 (5 years ago).
Company metadata: SlimWare Utilities Inc. Product metadata: lib-inappbrowser.
Signed by Slimware Utilities Holdings, Inc.. The signature is reported as valid, but signed files can still be bundled or abused.
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
- Use the hash and metadata below to verify the exact file identity.
- Review publisher, signature, paths, and PE details for inconsistencies.
- Run a local scan if the file appears unexpectedly or starts with Windows.
File context
lib-inappbrowser.dll#4F42701C4117ECC8 is a Windows file recorded in the ThreatInfo database. It is associated with lib-inappbrowser. The reported company name is SlimWare Utilities Inc. The current detection status is Undefined, based on the latest analysis from 2021-01-01 19:37:46 (5 years 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.
File Details
| Product Name: | lib-inappbrowser |
| Company Name: | SlimWare Utilities Inc |
| MD5: | c1059539f9aa321ea18acb43e18f3e25 |
| Size: | 140 KB |
| First Published: | 2020-03-01 20:13:10 (6 years ago) |
| Latest Published: | 2021-01-01 19:37:46 (5 years ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2021-01-01 19:37:46 (5 years ago) |
Overview
| Signed By: | Slimware Utilities Holdings, Inc. |
| Status: | Valid |
The signature on lib-inappbrowser.dll#4F42701C4117ECC8 is reported as valid. A valid signature helps confirm publisher identity, but it does not automatically make the file safe if the installer was bundled, abused, or downloaded from an untrusted source.
Common Places:
| %sysdrive%\nvidia corporation\adwcleaner\quarantine\v1\20190722.123434\20190722.123245\57 |
| %programfiles% |
ThreatInfo has observed lib-inappbrowser.dll#4F42701C4117ECC8 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.
Geographic signal
Observed country distribution
ThreatInfo has seen lib-inappbrowser.dll#4F42701C4117ECC8 across 1 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is United States with 100.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for lib-inappbrowser.dll#4F42701C4117ECC8 is Windows 10 with 66.7% 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.
Analysis
lib-inappbrowser.dll#4F42701C4117ECC8 is identified as pe for 32-bit systems. The subsystem is Windows CUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.
.NET Info:
| MVID: | a8fa3b1f-777e-4e44-a837-cb0099d31245 |
| Typelib ID: | c8c15499-922d-47e0-9027-3b53498a10ee |
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
6f5264fafc0afbd0106fde17cd666399
9b5409a18699e4201c709aae4a6c5e43
f1fc643edcc25dfbf1163bb317739de1
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.