GridinSoft Threat Intelligence

Teams_windows_x64.exe file report

Clean record File reputation report
MD5 6090136f7754c9bbce723a56d661b4f8
Latest seen 2022-11-25 23:05:20 (3 years ago)
First seen 2022-11-25 23:05:20 (3 years ago)
Size 122 MB
Product Microsoft Teams

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2022-11-25 23:05:20 (3 years ago); latest analysis 2022-11-25 23:05:20 (3 years ago).

Publisher context

Company metadata: Microsoft Corporation. Product metadata: Microsoft Teams.

Digital signature

Signed by Microsoft Corporation. ThreatInfo marks this publisher as trusted for this record.

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. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

Teams_windows_x64.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 Clean, based on the latest analysis from 2022-11-25 23:05:20 (3 years ago).

This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.

Product Name: Microsoft Teams
Company Name: Microsoft Corporation
MD5: 6090136f7754c9bbce723a56d661b4f8
Size: 122 MB
First Published: 2022-11-25 23:05:20 (3 years ago)
Latest Published: 2022-11-25 23:05:20 (3 years ago)
Status: Clean (on last analysis)
Analysis Date: 2022-11-25 23:05:20 (3 years ago)
Signed By: Microsoft Corporation
Status: Trusted Publisher

ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.

%profile%

ThreatInfo has observed Teams_windows_x64.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 Teams_windows_x64.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.

Teams_windows_x64.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 0x00014510
Image base 0x00400000

PE Sections:

Sections 5
Raw data 128304128

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

.text 215040 bytes · 0.2% of section data
MD5 07fe44e59b7d8618640b88e0fe145693
.rdata 89088 bytes · 0.1% of section data
MD5 1393703c3672871853284109ba5d1ec1
.data 6144 bytes · 0.0% of section data
MD5 ea4194ed93dbd47354fff2b0b95a296b
.rsrc 127981056 bytes · 99.7% of section data
Large raw data
MD5 b8aaff11c6ebfd6684dabf5f5f91fd20
.reloc 12800 bytes · 0.0% of section data
MD5 15f6aa50b5f1449df9ee9232c65dd555

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 hash is currently recorded as clean

Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.

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 6090136f7754c9bbce723a56d661b4f8.
  • 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.