GridinSoft Threat Intelligence

bdnc.dll file report

Clean record File reputation report
MD5 deb0a358b033a2f866719bf4a1cba7c7
Latest seen 2026-02-13 23:01:56 (3 months ago)
First seen 2020-08-24 10:10:48 (5 years ago)
Size 1 MB
Publisher Bitdefender
Signed by Bitdefender SRL

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2020-08-24 10:10:48 (5 years ago); latest analysis 2026-02-13 23:01:56 (3 months ago).

Publisher context

Company metadata: Bitdefender. Product metadata: BitDefender Nimbus Client.

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.

bdnc.dll is a Windows file recorded in the ThreatInfo database. It is associated with BitDefender Nimbus Client. The reported company name is Bitdefender. The current detection status is Clean, based on the latest analysis from 2026-02-13 23:01:56 (3 months 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 Nimbus Client
Company Name: Bitdefender
MD5: deb0a358b033a2f866719bf4a1cba7c7
Size: 1 MB
First Published: 2020-08-24 10:10:48 (5 years ago)
Latest Published: 2026-02-13 23:01:56 (3 months ago)
Status: Clean (on last analysis)
Analysis Date: 2026-02-13 23:01:56 (3 months 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.

%programfiles%\lavasoft\web companion\service

ThreatInfo has observed bdnc.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 91.7%
Windows 7 7.1%
Windows 8.1 0.6%
Windows 8 0.4%
Windows Vista 0.2%

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

bdnc.dll 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 0x000edc35
Image base 0x10000000

PE Sections:

Sections 5
Raw data 1394176

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

.text 1056256 bytes · 75.8% of section data
MD5 2f184d0ced687ea60c9d2d1d2896cb2d
.rdata 259584 bytes · 18.6% of section data
MD5 676f2f45f0e8d56363a7a227ec3f0907
.data 26112 bytes · 1.9% of section data
MD5 bd0363f233681778c35b6272636edafd
.rsrc 1024 bytes · 0.1% of section data
MD5 e21f6af03ed728a216ff81587f3c4ab9
.reloc 51200 bytes · 3.7% of section data
MD5 0e0c4d78aab24e1fd9f7f3ff68aa8e76

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 deb0a358b033a2f866719bf4a1cba7c7.
  • 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.