GridinSoft Threat Intelligence

IdcLdr.exe file report

Under review File reputation report
MD5 0c0fc7162953c162d1e6e4c1274412d3
Latest seen 2025-02-07 23:01:32 (a year ago)
First seen 2017-05-21 04:03:12 (8 years ago)
Size 153 KB
Publisher APN LLC.
Product IDC
Signed by APN LLC

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-21 04:03:12 (8 years ago); latest analysis 2025-02-07 23:01:32 (a year ago).

Publisher context

Company metadata: APN LLC.. Product metadata: IDC.

Digital signature

Signed by APN LLC. The signature is not reported as trusted and valid, which can indicate tampering, repackaging, or copied publisher data.

Aliases

This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.

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.

IdcLdr.exe is a Windows file recorded in the ThreatInfo database. It is associated with IDC. The reported company name is APN LLC.. The current detection status is Undefined, based on the latest analysis from 2025-02-07 23:01:32 (a year 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: IDC
Company Name: APN LLC.
MD5: 0c0fc7162953c162d1e6e4c1274412d3
Size: 153 KB
First Published: 2017-05-21 04:03:12 (8 years ago)
Latest Published: 2025-02-07 23:01:32 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-02-07 23:01:32 (a year ago)
Signed By: APN LLC
Status: Invalid (digital signature could be stolen or file could be patched)

The signature on IdcLdr.exe is not reported as trusted and valid. Invalid or suspicious signature data can indicate tampering, repackaging, or an unrelated file using copied publisher information.

%system%\config\systemprofile\appdata\local\microsoft\windows\temporary internet files\content.ie5\asktoolbarinstaller-orj-spe[1].7z\program files\askpartnernetwork\toolbar\updater\idc
%system%\config\systemprofile\appdata\local\microsoft\windows\inetcache\ie\asktoolbarinstaller-orj-spe[4].7z\program files\askpartnernetwork\toolbar\updater\idc
%system%\config\systemprofile\appdata\local\microsoft\windows\temporary internet files\content.ie5\asktoolbarinstaller-orj-spe[5].7z\program files\askpartnernetwork\toolbar\updater\idc
%localappdata%\askpartnernetwork\toolbar\updater\idc
%system%\config\systemprofile\appdata\local\microsoft\windows\temporary internet files\content.ie5\asktoolbarinstaller-orj-st-spe[1].7z\program files\askpartnernetwork\toolbar\updater\idc
%system%\config\systemprofile\appdata\local\microsoft\windows\temporary internet files\content.ie5\asktoolbarinstaller-orj-spe[2].7z\program files\askpartnernetwork\toolbar\updater\idc
%programfiles%\askpartnernetwork\toolbar\updater\idc
%programfiles%\askpartnernetwork\toolbar\orj-spe\source\program files\askpartnernetwork\toolbar\updater\idc
%sysdrive%\adwcleaner\quarantine\files\jqaitnsxquuquecyfyaonzouipasrxvq\toolbar\updater\idc
%system%\config\systemprofile\appdata\local\microsoft\windows\temporary internet files\content.ie5\asktoolbarinstaller-orj-spe[4].7z\program files\askpartnernetwork\toolbar\updater\idc

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

A0108990.exe A0108977.exe A0109000.exe IdcLdr.exe

This hash has been seen with multiple file names. Alternate names can appear when software is updated, copied between folders, packed by an installer, or deliberately renamed to avoid recognition. Compare the exact MD5 above before assuming two names refer to the same file.

Windows 7 70.5%
Windows 10 13.2%
Windows 8.1 10.5%
Windows XP 3.7%
Windows 8 1.6%
Windows Vista 0.5%

The most common operating system signal for IdcLdr.exe is Windows 7 with 70.5% 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.

IdcLdr.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 0x000061c2
Image base 0x00400000

PE Sections:

Sections 5
Raw data 149504

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

.text 71168 bytes · 47.6% of section data
MD5 23c577b88e0012a04f72d1174e5789ae
.rdata 15872 bytes · 10.6% of section data
MD5 ac716660c4bc78d1ba346e7d454545f2
.data 5120 bytes · 3.4% of section data
MD5 9d0e724d99ebf46be393794a4973386f
.rsrc 50176 bytes · 33.6% of section data
MD5 629003bef13e53365565a4b2a5804e0c
.reloc 7168 bytes · 4.8% of section data
MD5 da52c2cf39a44cf3d1a5a8abb0e8faf7

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 0c0fc7162953c162d1e6e4c1274412d3.
  • 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.