GridinSoft Threat Intelligence

cmnsusbser.sys file report

Under review File reputation report
MD5 2b3b8cbea1ba1bce5700607fbdb31034
Latest seen 2021-02-11 04:55:44 (5 years ago)
First seen 2021-02-11 04:55:44 (5 years ago)
Size 115 KB
Publisher Mobile Connector

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2021-02-11 04:55:44 (5 years ago); latest analysis 2021-02-11 04:55:44 (5 years ago).

Publisher context

Company metadata: Mobile Connector. Product metadata: USB Modem/Serial Device Driver.

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.

cmnsusbser.sys is a Windows file recorded in the ThreatInfo database. It is associated with USB Modem/Serial Device Driver. The reported company name is Mobile Connector. The current detection status is Undefined, based on the latest analysis from 2021-02-11 04:55:44 (5 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: USB Modem/Serial Device Driver
Company Name: Mobile Connector
MD5: 2b3b8cbea1ba1bce5700607fbdb31034
Size: 115 KB
First Published: 2021-02-11 04:55:44 (5 years ago)
Latest Published: 2021-02-11 04:55:44 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-02-11 04:55:44 (5 years ago)
%programfiles%\speedup\su-8650 3.5g mobile connect\driver

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

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

cmnsusbser.sys is identified as pe for 64-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 64-bit
Subsystem Native
Entry point 0x0001ba88
Image base 0x0000000000010000

PE Sections:

Sections 7
Raw data 117120

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

.text 105984 bytes · 90.5% of section data
MD5 226963bdd1dc81a5a3d6c688c5ca6173
.rdata 3072 bytes · 2.6% of section data
MD5 8328509f0c0733297c61b596e21117e3
.data 1280 bytes · 1.1% of section data
MD5 5703cf8375250ae8f82e24fb302212a8
.pdata 2176 bytes · 1.9% of section data
MD5 f8904a87bf4a02bac233cfc440e9711e
INIT 2816 bytes · 2.4% of section data
Uncommon name
MD5 e4b9b5b66100bd9c88545ef8fb1b4509
.rsrc 1536 bytes · 1.3% of section data
MD5 27760b3720c067f19131e2c5316a9388
.reloc 256 bytes · 0.2% of section data
MD5 a3ae09a7d71d1827d94363731671025d

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 2b3b8cbea1ba1bce5700607fbdb31034.
  • 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.