GridinSoft Threat Intelligence

DevMateKit.dll file report

Under review File reputation report
MD5 82b346856718eb33e599589f510fc4e0
Latest seen 2021-08-12 20:59:44 (4 years ago)
First seen 2017-11-03 18:07:58 (8 years ago)
Size 677 KB
Publisher MacPaw Inc.
Product DevMateKit
Signed by MacPaw INC

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-11-03 18:07:58 (8 years ago); latest analysis 2021-08-12 20:59:44 (4 years ago).

Publisher context

Company metadata: MacPaw Inc.. Product metadata: DevMateKit.

Digital signature

Signed by MacPaw INC. The signature is reported as valid, but signed files can still be bundled or abused.

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. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. Run a local scan if the file appears unexpectedly or starts with Windows.

DevMateKit.dll is a Windows file recorded in the ThreatInfo database. It is associated with DevMateKit. The reported company name is MacPaw Inc.. The current detection status is Undefined, based on the latest analysis from 2021-08-12 20:59:44 (4 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.

Product Name: DevMateKit
Company Name: MacPaw Inc.
MD5: 82b346856718eb33e599589f510fc4e0
Size: 677 KB
First Published: 2017-11-03 18:07:58 (8 years ago)
Latest Published: 2021-08-12 20:59:44 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-08-12 20:59:44 (4 years ago)
Signed By: MacPaw INC
Status: Valid

The signature on DevMateKit.dll 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.

%programfiles%\cleanmypc
%programfiles%

ThreatInfo has observed DevMateKit.dll 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 7 55.9%
Windows 10 41.2%
Windows 8.1 2.9%

The most common operating system signal for DevMateKit.dll is Windows 7 with 55.9% 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.

DevMateKit.dll is identified as pe for 32-bit systems. The subsystem is Windows CUI. 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 CUI
Entry point 0x000a75fa
Image base 0x10000000

.NET Info:

MVID: 0c53629d-31e2-416f-bf41-7904fd425c7e

PE Sections:

Sections 3
Raw data 679424

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

.text 677888 bytes · 99.8% of section data
MD5 7dc717b3c83a7345862bba09470ddaae
.rsrc 1024 bytes · 0.2% of section data
MD5 9e490c4307b63017efea9b196a7432a5
.reloc 512 bytes · 0.1% of section data
MD5 b584de8f8095e3d0c172280f9d18a9ca

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.

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 82b346856718eb33e599589f510fc4e0.
  • 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.