GridinSoft Threat Intelligence

IMBd223a50a-162b-4ed2-b6e6-84456c4d7176.dat file report

Under review File reputation report
MD5 69d0b65545efc90e116fdff3c4a6572d
Latest seen 2024-03-12 23:02:03 (2 years ago)
First seen 2017-07-27 14:07:59 (8 years ago)
Size 64 KB
Publisher Iminent

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-07-27 14:07:59 (8 years ago); latest analysis 2024-03-12 23:02:03 (2 years ago).

Publisher context

Company metadata: Iminent. Product metadata: Iminent.Services.Resources.

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.

IMBd223a50a-162b-4ed2-b6e6-84456c4d7176.dat is a Windows file recorded in the ThreatInfo database. It is associated with Iminent.Services.Resources. The reported company name is Iminent. The current detection status is Undefined, based on the latest analysis from 2024-03-12 23:02:03 (2 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: Iminent.Services.Resources
Company Name: Iminent
MD5: 69d0b65545efc90e116fdff3c4a6572d
Size: 64 KB
First Published: 2017-07-27 14:07:59 (8 years ago)
Latest Published: 2024-03-12 23:02:03 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-03-12 23:02:03 (2 years ago)
%commonappdata%\iminent\mediator\datas\raw\1
%commonappdata%\iminent\mediator\datas\raw

ThreatInfo has observed IMBd223a50a-162b-4ed2-b6e6-84456c4d7176.dat 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 83.3%
Windows Vista 16.7%

The most common operating system signal for IMBd223a50a-162b-4ed2-b6e6-84456c4d7176.dat is Windows 7 with 83.3% 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.

IMBd223a50a-162b-4ed2-b6e6-84456c4d7176.dat 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 0x0001199e
Image base 0x00400000

.NET Info:

MVID: 405d9404-0702-4230-96b2-b315bf2aa974
Typelib ID: ac0f3dca-ef44-49a2-a00f-60eaea1f6948

PE Sections:

Sections 3
Raw data 65536

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

.text 64000 bytes · 97.7% of section data
MD5 97a9bd0d0a82256fdf32346e649af0b1
.rsrc 1024 bytes · 1.6% of section data
MD5 cf3fb3173ed776fdc7ca5c7cfd7b31f5
.reloc 512 bytes · 0.8% of section data
MD5 2c9824c00226ed6c88f935224a58b1d5

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 69d0b65545efc90e116fdff3c4a6572d.
  • 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.