GridinSoft Threat Intelligence

spotify.exe file report

Clean record File reputation report
MD5 b71b39fa2f1080a6ae7788cc245a663a
Latest seen 2024-02-09 23:02:17 (2 years ago)
First seen 2024-02-09 23:02:17 (2 years ago)
Size 20 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-02-09 23:02:17 (2 years ago); latest analysis 2024-02-09 23:02:17 (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-02-09 23:02:17 (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: b71b39fa2f1080a6ae7788cc245a663a
Size: 20 MB
First Published: 2024-02-09 23:02:17 (2 years ago)
Latest Published: 2024-02-09 23:02:17 (2 years ago)
Status: Clean (on last analysis)
Analysis Date: 2024-02-09 23:02:17 (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 0x00052401
Image base 0x00400000

PE Sections:

Sections 4
Raw data 21137408

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

.text 11481600 bytes · 54.3% of section data
Large raw data
MD5 1bf82e953c7b401a460864004747c107
.rdata 2977280 bytes · 14.1% of section data
MD5 bc41950ca7d59adffd3c05bcd9d79b68
.data 6618624 bytes · 31.3% of section data
Large raw data
MD5 dc74e313ef196cb715ba566dce52c751
.rsrc 59904 bytes · 0.3% of section data
MD5 117032c30ac884b35edbea9d29b9da68

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 b71b39fa2f1080a6ae7788cc245a663a.
  • 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.