GridinSoft Threat Intelligence

ew_jucdcacm.sys file report

Under review File reputation report
MD5 568a34809e3c4afb26e0d3b2ed79495a
Latest seen 2024-08-14 23:01:45 (2 years ago)
First seen 2020-08-24 18:21:29 (5 years ago)
Size 93 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-08-24 18:21:29 (5 years ago); latest analysis 2024-08-14 23:01:45 (2 years ago).

Publisher context

Company metadata: Huawei Technologies Co., Ltd.. Product metadata: ew_jucdcacm Driver (x86).

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. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. Run a local scan if the file appears unexpectedly or starts with Windows.

ew_jucdcacm.sys is a Windows file recorded in the ThreatInfo database. It is associated with ew_jucdcacm Driver (x86). The reported company name is Huawei Technologies Co., Ltd.. The current detection status is Undefined, based on the latest analysis from 2024-08-14 23:01:45 (2 years ago).

ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.

Product Name: ew_jucdcacm Driver (x86)
Company Name: Huawei Technologies Co., Ltd.
MD5: 568a34809e3c4afb26e0d3b2ed79495a
Size: 93 KB
First Published: 2020-08-24 18:21:29 (5 years ago)
Latest Published: 2024-08-14 23:01:45 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-08-14 23:01:45 (2 years ago)
%programfiles%\claro\driver\driver

ThreatInfo has observed ew_jucdcacm.sys 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 50.0%
Windows 10 50.0%

The most common operating system signal for ew_jucdcacm.sys is Windows 7 with 50.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.

ew_jucdcacm.sys is identified as pe for 32-bit systems. The subsystem is Native. 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 Native
Entry point 0x0000ac14
Image base 0x00010000

PE Sections:

Sections 7
Raw data 94592

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

.text 74240 bytes · 78.5% of section data
MD5 7add2dc3dc6f06dcc7da8e8ea19ef443
.rdata 1408 bytes · 1.5% of section data
MD5 15cdbf398c1b2d47f49d6ab03c9a6081
.data 2560 bytes · 2.7% of section data
MD5 0d17d6adbd6bb2cbfc7615c4f925910a
PAGE 5888 bytes · 6.2% of section data
Uncommon name
MD5 b28d3d5c8bd12290a0c88271d43cacd0
INIT 2176 bytes · 2.3% of section data
Uncommon name
MD5 ab6e2bb0e6e8ac51f14166249a187148
.rsrc 1024 bytes · 1.1% of section data
MD5 1dda3a5024d91457a54d3c8274cd6773
.reloc 7296 bytes · 7.7% of section data
MD5 6bd394ea138e8be6ad2262b66003c123

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 file is still under review

ThreatInfo has not assigned a final verdict yet. Compare the file hash, location, signature, and publisher before trusting the file on a production system.

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 568a34809e3c4afb26e0d3b2ed79495a.
  • 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.