GridinSoft Threat Intelligence
Squirrel.exe file report
Why it matters
Evidence available for this file
No final classification is available yet.
First seen 2023-04-08 23:20:35 (3 years ago); latest analysis 2023-04-08 23:24:08 (3 years ago).
Company metadata: Microsoft Corporation. Product metadata: Microsoft Teams.
Signed by Microsoft 3rd Party Application Component;Microsoft Corporation. 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
Squirrel.exe is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft Teams. The reported company name is Microsoft Corporation. The current detection status is Undefined, based on the latest analysis from 2023-04-08 23:24:08 (3 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: | Microsoft Teams |
| Company Name: | Microsoft Corporation |
| MD5: | 9de1230a807cb773e08ba55d74cc8b92 |
| Size: | 1 MB |
| First Published: | 2023-04-08 23:20:35 (3 years ago) |
| Latest Published: | 2023-04-08 23:24:08 (3 years ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2023-04-08 23:24:08 (3 years ago) |
Overview
| Signed By: | Microsoft 3rd Party Application Component;Microsoft Corporation |
| Status: | Valid |
The signature on Squirrel.exe 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%\drive d\data van stick\paulda\appdata\local\microsoft\teams |
| %sysdrive%\drive d\data van stick\2de stick\paulda\appdata\local\microsoft\teams |
| %sysdrive%\drive d\data van stick\2de stick\paulda\appdata\local\microsoft |
| %sysdrive%\drive d\data van stick\paulda\appdata\local\microsoft |
ThreatInfo has observed Squirrel.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.
Geographic signal
Observed country distribution
ThreatInfo has seen Squirrel.exe 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 Squirrel.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.
Analysis
Squirrel.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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
f0189e824cd5716ea5a5933742a444f1
8a62df848f79ebbb11a532bf67cb828a
cabb9e7be4d33438558a56b9fb0d66c9
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.