GridinSoft Threat Intelligence

atcuf32.dll file report

Clean record File reputation report
MD5 0f542c11f7ad3befea7592c108c5a180
Latest seen 2021-12-26 21:17:50 (4 years ago)
First seen 2021-12-26 21:17:50 (4 years ago)
Size 916 KB
Signed by Bitdefender SRL

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-12-26 21:17:50 (4 years ago); latest analysis 2021-12-26 21:17:50 (4 years ago).

Publisher context

Company metadata: Bitdefender S.R.L. Bucharest, ROMANIA. Product metadata: Bitdefender® ATC.

Digital signature

Signed by Bitdefender SRL. 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.

atcuf32.dll is a Windows file recorded in the ThreatInfo database. It is associated with Bitdefender® ATC. The reported company name is Bitdefender S.R.L. Bucharest, ROMANIA. The current detection status is Clean, based on the latest analysis from 2021-12-26 21:17:50 (4 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: Bitdefender® ATC
Company Name: Bitdefender S.R.L. Bucharest, ROMANIA
MD5: 0f542c11f7ad3befea7592c108c5a180
Size: 916 KB
First Published: 2021-12-26 21:17:50 (4 years ago)
Latest Published: 2021-12-26 21:17:50 (4 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-12-26 21:17:50 (4 years ago)
Signed By: Bitdefender SRL
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.

%commonappdata%\bromium\bem

ThreatInfo has observed atcuf32.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 10 100.0%

The most common operating system signal for atcuf32.dll is Windows 10 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.

atcuf32.dll 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 0x00008380
Image base 0x10000000

PE Sections:

Sections 5
Raw data 923136

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

.text 354304 bytes · 38.4% of section data
MD5 1be31a804b1bcb51932f3a8571a215fc
.rdata 463360 bytes · 50.2% of section data
MD5 f5a146e38b1eec39bb19e5abbc23b548
.data 53248 bytes · 5.8% of section data
MD5 2669a06d00e275c6c5b063f126efd48d
.rsrc 1536 bytes · 0.2% of section data
MD5 ab01648e949d013ee339811fb817b9d2
.reloc 50688 bytes · 5.5% of section data
MD5 c98134a9ed941d94677714bc7ef1db11

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