DrvMonX86.sys threat report

MD5 bf2558840c8358f6bacd74cb2f06a139
Latest seen 2021-08-28 20:31:24 (4 years ago)
First seen 2020-09-16 22:20:37 (5 years ago)
Size 139 KB
Publisher Outbyte
Product DrvMon Driver

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as PUP.Outbyte. Download GridinSoft Anti-Malware to scan the device, confirm whether this file is present, and remove the detected object if it is found.

Detection name
PUP.Outbyte
Recommended action
Scan and remove
Last analysis
2021-08-28 20:31:24 (4 years ago)
File hash
bf2558840c8358f6bacd74cb2f06a139
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as PUP.Outbyte.

Timeline

First seen 2020-09-16 22:20:37 (5 years ago); latest analysis 2021-08-28 20:31:24 (4 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. Compare the MD5 above with the file found on the device.
  2. Check whether the file appears in the observed locations or under one of the alternate names.
  3. Run GridinSoft Anti-Malware to confirm the detection and remove the file if it is present.

DrvMonX86.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 PUP.Outbyte, based on the latest analysis from 2021-08-28 20:31:24 (4 years ago).

If DrvMonX86.sys appears on your computer unexpectedly, treat it as suspicious. Check its location, digital signature, and recent system changes before allowing it to run. A full anti-malware scan is recommended when this file is detected as PUP.Outbyte.

Product Name: DrvMon Driver
Company Name: Outbyte
MD5: bf2558840c8358f6bacd74cb2f06a139
Size: 139 KB
First Published: 2020-09-16 22:20:37 (5 years ago)
Latest Published: 2021-08-28 20:31:24 (4 years ago)
Status: PUP.Outbyte (on last analysis)
Analysis Date: 2021-08-28 20:31:24 (4 years ago)
DrvMonX86.sys detection screenshot

The screenshot is a visual record of a GridinSoft Anti-Malware detection for this sample. Use the hash and metadata above as the primary identifiers when comparing the file on your system.

The signature on DrvMonX86.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
%programfiles%\outbyte
%programfiles%\outbyte
%programfiles%\outbyte
%programfiles%\outbyte
%programfiles%\outbyte
%programfiles%\outbyte

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

10.0%
6.7%
6.7%
6.7%
5.0%
5.0%
5.0%
5.0%
5.0%
3.3%
3.3%
3.3%
3.3%
3.3%
3.3%
3.3%
1.7%
1.7%
1.7%
1.7%
1.7%
1.7%
1.7%
1.7%
1.7%
1.7%
1.7%
1.7%
1.7%

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

Windows 10 69.4%
Windows 7 29.0%
Windows 8.1 1.6%

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

DrvMonX86.sys is identified as pe for 32 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: 32
Image Base: 0x00400000
Entry Address: 0x0001c180

PE Sections:

Name Size of data MD5
.text 88064 3e8a6d752521b484a2116422855e5f04
.rdata 11776 8d2e495f2b659d24efed21deafbc91f7
.data 1024 0d2740f5aeca92bd280e1cce1f89e5e1
PAGE 2560 d143f00d05798a9a29fc3a8cbc25c4dd
INIT 4608 63513413ad8bfbdb901090014e5f12ca
.rsrc 1536 7a76288c9197e256cc36df09fa5a0393
.reloc 5120 205f2a9a1f60bd8723e5555730dba563

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: