GridinSoft Threat Intelligence

TABCTL32.OCX file report

Clean record File reputation report
MD5 2bae02cd88d9ef0c03bdab250904f802
Latest seen 2023-07-16 23:39:49 (2 years ago)
First seen 2018-06-15 03:10:45 (7 years ago)
Size 204 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2018-06-15 03:10:45 (7 years ago); latest analysis 2023-07-16 23:39:49 (2 years ago).

Publisher context

Company metadata: Microsoft Corporation. Product metadata: TabCtl32 Object Library.

Digital signature

Signed by Microsoft Corporation. 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.

TABCTL32.OCX is a Windows file recorded in the ThreatInfo database. It is associated with TabCtl32 Object Library. The reported company name is Microsoft Corporation. The current detection status is Clean, based on the latest analysis from 2023-07-16 23:39:49 (2 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: TabCtl32 Object Library
Company Name: Microsoft Corporation
MD5: 2bae02cd88d9ef0c03bdab250904f802
Size: 204 KB
First Published: 2018-06-15 03:10:45 (7 years ago)
Latest Published: 2023-07-16 23:39:49 (2 years ago)
Status: Clean (on last analysis)
Analysis Date: 2023-07-16 23:39:49 (2 years ago)
Signed By: Microsoft Corporation
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%
%commonappdata%\pack3264\amoi
%commonappdata%\pack3264

ThreatInfo has observed TABCTL32.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 10 92.3%
Windows 7 7.7%

The most common operating system signal for TABCTL32.OCX is Windows 10 with 92.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.

TABCTL32.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 0x00008396
Image base 0x212f0000

PE Sections:

Sections 4
Raw data 202240

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

.text 139264 bytes · 68.9% of section data
MD5 05d85ea7369b54694e1925674ed24c57
.data 14336 bytes · 7.1% of section data
MD5 b73d27b14d5bb2fbf433848f2ba0ff8d
.rsrc 40448 bytes · 20.0% of section data
MD5 e7b6062e95592b0e713b5ca821d23477
.reloc 8192 bytes · 4.1% of section data
MD5 7559e044b800eb9e57ed1d4a5d063f95

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