GridinSoft Threat Intelligence

mod7700.sys file report

Under review File reputation report
MD5 15e399875c850b54fc253a2323ad8021
Latest seen 2024-08-14 23:01:41 (2 years ago)
First seen 2017-07-04 02:10:37 (8 years ago)
Size 978 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:37 (8 years ago); latest analysis 2024-08-14 23:01:41 (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:41 (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: 15e399875c850b54fc253a2323ad8021
Size: 978 KB
First Published: 2017-07-04 02:10:37 (8 years ago)
Latest Published: 2024-08-14 23:01:41 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-08-14 23:01:41 (2 years ago)
%programfiles%\claro\driver\driver\x64
%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.

82.6%
17.4%

The strongest geographic signal for this file is Brazil with 82.6% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

Windows 10 43.5%
Windows 7 30.4%
Windows 8.1 26.1%

The most common operating system signal for mod7700.sys is Windows 10 with 43.5% 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 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 0x000f3064
Image base 0x0000000000010000

PE Sections:

Sections 7
Raw data 1000448

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

.text 291840 bytes · 29.2% of section data
MD5 a06f2916219e3300aa30e09bd37f713c
.rdata 244224 bytes · 24.4% of section data
MD5 2d41db3c18d8dc91719406a7abc77ec7
.data 432640 bytes · 43.2% of section data
MD5 01c87df3ad0c814dbab79905d517300c
.pdata 10752 bytes · 1.1% of section data
MD5 0d6c99c0f59e56685036b13a804a01bb
INIT 3584 bytes · 0.4% of section data
Uncommon name
MD5 b53456920abd8e407cb81c8659f019ff
.rsrc 1024 bytes · 0.1% of section data
MD5 a484ae3ae74cbd4c8cc561a808d28296
.reloc 16384 bytes · 1.6% of section data
MD5 7d6a7da8b54315a01825dd0f8e06c253

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 15e399875c850b54fc253a2323ad8021.
  • 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.