GridinSoft Threat Intelligence

brciser.dll file report

Clean record File reputation report
MD5 0392b62bb7a3c322b69d760af2e2352c
Latest seen 2021-01-14 16:36:00 (5 years ago)
First seen 2021-01-14 16:36:00 (5 years ago)
Size 18 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-01-14 16:36:00 (5 years ago); latest analysis 2021-01-14 16:36:00 (5 years ago).

Publisher context

Company metadata: Brother Industries Ltd.. Product metadata: Windows (R) Codename Longhorn DDK driver.

Digital signature

Signed by Brother Industries, Ltd.. 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.

brciser.dll is a Windows file recorded in the ThreatInfo database. It is associated with Windows (R) Codename Longhorn DDK driver. The reported company name is Brother Industries Ltd.. The current detection status is Clean, based on the latest analysis from 2021-01-14 16:36:00 (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: Windows (R) Codename Longhorn DDK driver
Company Name: Brother Industries Ltd.
MD5: 0392b62bb7a3c322b69d760af2e2352c
Size: 18 KB
First Published: 2021-01-14 16:36:00 (5 years ago)
Latest Published: 2021-01-14 16:36:00 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-01-14 16:36:00 (5 years ago)
Signed By: Brother Industries, Ltd.
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.

%localappdata%\slimware utilities inc\slimdrivers\backups\20200501t081141684142\usb\vid_04f9&pid_02b4&mi_02

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

brciser.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 0x00001de8
Image base 0x02000000

PE Sections:

Sections 4
Raw data 10752

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

.text 7168 bytes · 66.7% of section data
MD5 31f4cb8817d2d2cfb210fc02eb0d4a9b
.data 1024 bytes · 9.5% of section data
MD5 1da37e082b64bbd513850e2a1869a074
.rsrc 1536 bytes · 14.3% of section data
MD5 5d23aaee4f5f82baa9f5aa52be7b2dbb
.reloc 1024 bytes · 9.5% of section data
MD5 2ebb318cf8c6e49ff6f92cdd26fe5b20

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 0392b62bb7a3c322b69d760af2e2352c.
  • 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.