GridinSoft Threat Intelligence

Mousbser.sys file report

Under review File reputation report
MD5 8a79748b1fbe6ff8da5eb87a15217dfb
Latest seen 2022-06-20 23:47:58 (3 years ago)
First seen 2022-06-20 23:24:21 (3 years ago)
Size 101 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2022-06-20 23:24:21 (3 years ago); latest analysis 2022-06-20 23:47:58 (3 years ago).

Publisher context

Company metadata: Motorola Incorporated. Product metadata: Motorola Incorporated 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.

Mousbser.sys is a Windows file recorded in the ThreatInfo database. It is associated with Motorola Incorporated USB Modem/Serial Device Driver. The reported company name is Motorola Incorporated. The current detection status is Undefined, based on the latest analysis from 2022-06-20 23:47:58 (3 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: Motorola Incorporated USB Modem/Serial Device Driver
Company Name: Motorola Incorporated
MD5: 8a79748b1fbe6ff8da5eb87a15217dfb
Size: 101 KB
First Published: 2022-06-20 23:24:21 (3 years ago)
Latest Published: 2022-06-20 23:47:58 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-06-20 23:47:58 (3 years ago)
%sysdrive%\تعريفات كل الاجهزة\sdi_update\drivers\dp_telephone_16104.7z\motorola\forced
%commondir%\motorola shared\mobile drivers

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

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

Mousbser.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 0x00016e85
Image base 0x00010000

PE Sections:

Sections 6
Raw data 102400

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

.text 90752 bytes · 88.6% of section data
MD5 4361ae5342c7b6faa434b0cf20975ec7
.rdata 1024 bytes · 1.0% of section data
MD5 1e11713f37534954fa23fbe6ab680ce8
.data 896 bytes · 0.9% of section data
MD5 bbd71b26e85fde7ded5b29fd4dadcf3b
INIT 2560 bytes · 2.5% of section data
Uncommon name
MD5 e8f151b2833fa7e412ee46bf8e28c64a
.rsrc 1664 bytes · 1.6% of section data
MD5 ae06d5c0019af94f63a547e55cec9861
.reloc 5504 bytes · 5.4% of section data
MD5 81ea1ef140dae9cec57812330768263a

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 8a79748b1fbe6ff8da5eb87a15217dfb.
  • 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.