GridinSoft Threat Intelligence

IDrop.ocx file report

Clean record File reputation report
MD5 0192fffbc3557139282e887fb61d3295
Latest seen 2021-01-08 20:48:22 (5 years ago)
First seen 2018-09-14 23:09:04 (7 years ago)
Size 338 KB
Publisher Autodesk, Inc.
Product i-drop control
Signed by Autodesk, Inc

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2018-09-14 23:09:04 (7 years ago); latest analysis 2021-01-08 20:48:22 (5 years ago).

Publisher context

Company metadata: Autodesk, Inc.. Product metadata: i-drop control.

Digital signature

Signed by Autodesk, Inc. 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.

IDrop.ocx is a Windows file recorded in the ThreatInfo database. It is associated with i-drop control. The reported company name is Autodesk, Inc.. The current detection status is Clean, based on the latest analysis from 2021-01-08 20:48: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: i-drop control
Company Name: Autodesk, Inc.
MD5: 0192fffbc3557139282e887fb61d3295
Size: 338 KB
First Published: 2018-09-14 23:09:04 (7 years ago)
Latest Published: 2021-01-08 20:48:22 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-01-08 20:48:22 (5 years ago)
Signed By: Autodesk, Inc
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.

%programfiles%\acad2007\bin\acadfeui\windows
%temp%\windows

ThreatInfo has observed IDrop.ocx 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 100.0%

The most common operating system signal for IDrop.ocx is Windows 7 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.

IDrop.ocx 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 0x0001f807
Image base 0x5e190000

PE Sections:

Sections 5
Raw data 339456

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

.text 183296 bytes · 54.0% of section data
MD5 b5b39b419411dd95b3e2374a8d1a8a96
.rdata 35840 bytes · 10.6% of section data
MD5 6394db83021892624c8f51edcd7bb406
.data 6144 bytes · 1.8% of section data
MD5 1f13a1b31130463c7c2d3dea7e033bec
.rsrc 97792 bytes · 28.8% of section data
MD5 7b0a63636051d7767b54a8f87214f774
.reloc 16384 bytes · 4.8% of section data
MD5 78e2db0182d3ec38e275785982f85faf

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 0192fffbc3557139282e887fb61d3295.
  • 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.