GridinSoft Threat Intelligence

spotify.exe file report

Clean record File reputation report
MD5 74b12cbc5d8d3de2c0f9fab92c093087
Latest seen 2024-06-30 23:00:51 (2 years ago)
First seen 2024-06-30 23:00:51 (2 years ago)
Size 25 MB
Publisher Spotify Ltd
Product Spotify
Signed by Spotify AB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2024-06-30 23:00:51 (2 years ago); latest analysis 2024-06-30 23:00:51 (2 years ago).

Publisher context

Company metadata: Spotify Ltd. Product metadata: Spotify.

Digital signature

Signed by Spotify AB. 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.

spotify.exe is a Windows file recorded in the ThreatInfo database. It is associated with Spotify. The reported company name is Spotify Ltd. The current detection status is Clean, based on the latest analysis from 2024-06-30 23:00:51 (2 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: Spotify
Company Name: Spotify Ltd
MD5: 74b12cbc5d8d3de2c0f9fab92c093087
Size: 25 MB
First Published: 2024-06-30 23:00:51 (2 years ago)
Latest Published: 2024-06-30 23:00:51 (2 years ago)
Status: Clean (on last analysis)
Analysis Date: 2024-06-30 23:00:51 (2 years ago)
Signed By: Spotify AB
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.

%appdata%

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

spotify.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 0x00068271
Image base 0x00400000

PE Sections:

Sections 6
Raw data 26625536

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

.text 14272512 bytes · 53.6% of section data
Large raw data
MD5 7af774a1fd9d843c8d5ac3625501b6ad
.rdata 3724288 bytes · 14.0% of section data
MD5 2e2c05f93f716ff37b8019d14ae84c0d
.data 7745536 bytes · 29.1% of section data
Large raw data
MD5 af061699bb33dfdf231eaae0aa8f596a
prot 512 bytes · 0.0% of section data
Uncommon name
MD5 bf619eac0cdf3f68d496ea9344137e8b
.rsrc 73728 bytes · 0.3% of section data
MD5 8c34efc1b656b984c644f1f60ca5f12b
.reloc 808960 bytes · 3.0% of section data
MD5 bd3c25c9c9f97d079550a9e081165fa9

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 74b12cbc5d8d3de2c0f9fab92c093087.
  • 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.