DrvMonX64.sys file report

MD5 cd6ddad0c72d15758d44fd694bd69216
Latest seen 2024-04-07 23:01:44 (2 years ago)
First seen 2020-01-22 04:19:44 (6 years ago)
Size 176 KB
Publisher Outbyte
Product DrvMon Driver

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-01-22 04:19:44 (6 years ago); latest analysis 2024-04-07 23:01:44 (2 years ago).

Publisher context

Company metadata: Outbyte. Product metadata: DrvMon Driver.

Digital signature

Signed by Outbyte Computing Pty Ltd;Microsoft Windows Hardware Compatibility Publisher. The signature is reported as valid, but signed files can still be bundled or abused.

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.

DrvMonX64.sys is a Windows file recorded in the ThreatInfo database. It is associated with DrvMon Driver. The reported company name is Outbyte. The current detection status is Undefined, based on the latest analysis from 2024-04-07 23:01:44 (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: DrvMon Driver
Company Name: Outbyte
MD5: cd6ddad0c72d15758d44fd694bd69216
Size: 176 KB
First Published: 2020-01-22 04:19:44 (6 years ago)
Latest Published: 2024-04-07 23:01:44 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-04-07 23:01:44 (2 years ago)

The signature on DrvMonX64.sys is reported as valid. A valid signature helps confirm publisher identity, but it does not automatically make the file safe if the installer was bundled, abused, or downloaded from an untrusted source.

%programfiles%\outbyte
%programfiles%\outbyte
%programfiles%\outbyte
%programfiles%\outbyte
%sysdrive%\pc repair
%programfiles%\outbyte
%programfiles%\outbyte
%programfiles%\outbyte
%programfiles%\outbyte
%programfiles%\outbyte

ThreatInfo has observed DrvMonX64.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.

11.8%
11.8%
6.9%
5.9%
5.9%
5.9%
4.9%
3.9%
3.9%
3.9%
2.9%
2.9%
2.9%
2.0%
2.0%
2.0%
2.0%
2.0%
2.0%
1.0%
1.0%
1.0%
1.0%
1.0%
1.0%
1.0%
1.0%
1.0%
1.0%
1.0%
1.0%
1.0%
1.0%
1.0%

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

Windows 10 83.5%
Windows 7 13.8%
Windows 8.1 1.8%
Windows 8 0.9%

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

DrvMonX64.sys is identified as pe for 64 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.

Subsystem: Native
PE Type: pe
OS Bitness: 64
Image Base: 0x0000000140000000
Entry Address: 0x000271c0

PE Sections:

Name Size of data MD5
.text 108032 431f1e2886ef446df9af7a7cbb00c733
.rdata 23552 a757cf33c6b7d1a3cb1ee92777fbce82
.data 1536 d8153a5cded9368d5a8b8bb74e7a5fe6
.pdata 9216 db1236ab34f2683c51c2a26f52659888
PAGE 2560 934a9dca1d64ea6439e4e43849d26355
INIT 5120 b05f5b82d7f6ba08e46935697f597ca1
.rsrc 1536 cefbc7471b660ebf91cd6f4dfa78e20e
.reloc 512 a98e3c0988803e8ecec81dee38e89358

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.

More information: