GridinSoft Threat Intelligence

ew_jucdcecm.sys file report

Under review File reputation report
MD5 73093e73236b1a248eebb52acc009deb
Latest seen 2024-08-14 23:01:42 (2 years ago)
First seen 2020-08-24 18:23:38 (5 years ago)
Size 66 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

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

Publisher context

Company metadata: Huawei Technologies Co., Ltd.. Product metadata: ew_jucdcndis 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_jucdcecm.sys is a Windows file recorded in the ThreatInfo database. It is associated with ew_jucdcndis 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:42 (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_jucdcndis Driver (x86)
Company Name: Huawei Technologies Co., Ltd.
MD5: 73093e73236b1a248eebb52acc009deb
Size: 66 KB
First Published: 2020-08-24 18:23:38 (5 years ago)
Latest Published: 2024-08-14 23:01:42 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-08-14 23:01:42 (2 years ago)
%programfiles%\claro\driver\driver

ThreatInfo has observed ew_jucdcecm.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_jucdcecm.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_jucdcecm.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 0x00001830
Image base 0x00010000

PE Sections:

Sections 7
Raw data 66432

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

.text 49792 bytes · 75.0% of section data
MD5 ff614a3f411a0371ab16d044272cb281
.rdata 640 bytes · 1.0% of section data
MD5 81bd3dd90068fd7b256ed9cf68c1c9f3
.data 2560 bytes · 3.9% of section data
MD5 03ca28fc831d74850951beaaf233c0d3
PAGE 5760 bytes · 8.7% of section data
Uncommon name
MD5 79e1cab39866c8dfa2c3ea43d634db71
INIT 2304 bytes · 3.5% of section data
Uncommon name
MD5 9c902cd913d7cb4fb7eef7b3869a37ee
.rsrc 1024 bytes · 1.5% of section data
MD5 c369ad2041860bff6c23d1efcf7008b5
.reloc 4352 bytes · 6.6% of section data
MD5 dd8b5dacb10eee20aff650cb2850c90f

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 73093e73236b1a248eebb52acc009deb.
  • 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.