GridinSoft Threat Intelligence

mod7700.sys file report

Under review File reputation report
MD5 f5f91fa6fe7e4af269873caa5f5b370e
Latest seen 2024-08-14 23:01:47 (2 years ago)
First seen 2017-07-04 02:10:38 (8 years ago)
Size 841 KB
Publisher DiBcom SA

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-07-04 02:10:38 (8 years ago); latest analysis 2024-08-14 23:01:47 (2 years ago).

Publisher context

Company metadata: DiBcom SA. Product metadata: DiBcom AVSTREAM BDA 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.

mod7700.sys is a Windows file recorded in the ThreatInfo database. It is associated with DiBcom AVSTREAM BDA driver. The reported company name is DiBcom SA. The current detection status is Undefined, based on the latest analysis from 2024-08-14 23:01:47 (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: DiBcom AVSTREAM BDA driver
Company Name: DiBcom SA
MD5: f5f91fa6fe7e4af269873caa5f5b370e
Size: 841 KB
First Published: 2017-07-04 02:10:38 (8 years ago)
Latest Published: 2024-08-14 23:01:47 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-08-14 23:01:47 (2 years ago)
%programfiles%\claro\driver\driver\x86
%programfiles%\claro\driver\driver
%programfiles%\tattoo\driver\driver

ThreatInfo has observed mod7700.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 41.7%
Windows 8.1 29.2%
Windows 7 29.2%

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

mod7700.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 0x000cc63e
Image base 0x00010000

PE Sections:

Sections 6
Raw data 860544

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

.text 217728 bytes · 25.3% of section data
MD5 eeeaa79f94ec1dae398f57b6c0cbf5e4
.rdata 199040 bytes · 23.1% of section data
MD5 23a212a266553687a931f4bfe13beec7
.data 419200 bytes · 48.7% of section data
MD5 7edd80baeece43dcf0f14def3e2223c6
INIT 3328 bytes · 0.4% of section data
Uncommon name
MD5 ff3ec74b2d87dcba0b9dc1380167ddec
.rsrc 1024 bytes · 0.1% of section data
MD5 e7dd2c33757360ea46d93f4775e87fad
.reloc 20224 bytes · 2.4% of section data
MD5 2707291e537850a139cb74dd2be2d38a

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 f5f91fa6fe7e4af269873caa5f5b370e.
  • 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.