MD5 2fce85a3fa012c61ee2d1cc449829258
Latest seen 2021-02-21 04:05:22 (5 years ago)
First seen 2021-02-21 04:05:22 (5 years ago)
Size 2 MB
Publisher Paragon
Signed by Kaspersky Lab

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-02-21 04:05:22 (5 years ago); latest analysis 2021-02-21 04:05:22 (5 years ago).

Publisher context

Company metadata: Paragon. Product metadata: Sysinternals Procmon.

Digital signature

Signed by Kaspersky Lab. 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.

5870.tmp.exe is a Windows file recorded in the ThreatInfo database. It is associated with Sysinternals Procmon. The reported company name is Paragon. The current detection status is Clean, based on the latest analysis from 2021-02-21 04:05:22 (5 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: Sysinternals Procmon
Company Name: Paragon
MD5: 2fce85a3fa012c61ee2d1cc449829258
Size: 2 MB
First Published: 2021-02-21 04:05:22 (5 years ago)
Latest Published: 2021-02-21 04:05:22 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-02-21 04:05:22 (5 years ago)
Signed By: Kaspersky Lab
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.

%temp%

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

5870.tmp.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 0x0048a058
Image base 0x00400000

PE Sections:

Sections 7
Raw data 2761728

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

2560 bytes · 0.1% of section data
Uncommon name
MD5 307c60d77894b5ef38df6e1ed1f97caa
1024 bytes · 0.0% of section data
Uncommon name
MD5 c26bdf9496f0e2690f22ffeb864afcb3
512 bytes · 0.0% of section data
Uncommon name
MD5 6f8736fba52f0720d9ff5cfa6d4d8983
.idata 512 bytes · 0.0% of section data
MD5 404403365dcb4a9a6bff62a32565ee50
.rsrc 1536 bytes · 0.1% of section data
MD5 b7b9ed62ed5544ef4eb8826b6a9409cb
.themida 0 bytes · 0.0% of section data
Uncommon name
MD5 d41d8cd98f00b204e9800998ecf8427e
.boot 2755584 bytes · 99.8% of section data
Uncommon name
MD5 fc9835224509aa4b9e9bfa631079646a

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 2fce85a3fa012c61ee2d1cc449829258.
  • 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.