ArgusMonitor.sys - Suspicious (30/100) - DriverShield Analysis

Analysis of ArgusMonitor.sys: suspicious verdict, risk score 30/100. 0 YARA matches, 0/75 multi-engine detections. SHA256 bd62fa2cb145750f. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

ArgusMonitor.sys - Analysis Report

DriverShield analyzed the Windows kernel driver ArgusMonitor.sys and assigned a verdict of Suspicious with a composite risk score of 30/100, indicating some risk signals warranting review (30-59 band).

VerdictSuspicious (30/100)
YARA matches0
Multi-engine detections0 / 75
File size67272 bytes
Code-signing signerMicrosoft Windows Hardware Compatibility Publisher
Analyzed2026-04-02
SHA256bd62fa2cb145750fd4214f0ca57f3b314303791305e0b971510f796c0ff88247
SHA19f40a74730755974643e9d7957dad82449bc21fc
MD5d34108dc3a0b79bec1eed11761434139

Driver identity

Version resource data embedded in the ArgusMonitor.sys PE header, as extracted by the analysis engine.

File descriptionArgus Monitor Hardware Access Driver
ProductArgus Monitor Driver
CompanyArgotronic eGbR
Original filenameArgusMonitor.sys
Internal nameArgusMonitor.sys
File version3.04.0
CopyrightCopyright (C) 2008-2026 Argotronic eGbR. All rights reserved.

How the 30/100 score breaks down

Each component is scored 0-100 and then weighted into the composite. See the analysis methodology for the exact formula.

ComponentSub-score
Multi-engine consensus0 / 100
YARA signature matches0 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface90 / 100
Known-vulnerable corpus0 / 100
Code-signing state0 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (25)

Kernel-mode APIs resolved from the Import Address Table of ArgusMonitor.sys, ranked by exploitation relevance.

APIRiskWhy it matters
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
HalSetBusDataByOffsethighPotentially dangerous - could be used for privilege escalation or security bypass
HalGetBusDataByOffsethighPotentially dangerous - could be used for privilege escalation or security bypass
ZwWriteFilemediumModerate risk - system modification capability
IoGetDeviceObjectPointermediumModerate risk - system modification capability
MmUnmapIoSpacemediumModerate risk - system modification capability
ZwSetInformationFilemediumModerate risk - system modification capability
ZwCloselowStandard kernel API - generally benign
ZwQueryInformationFilelowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
ZwReadFilelowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
IoBuildDeviceIoControlRequestlowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
ExAllocatePool2lowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign
KeDelayExecutionThreadlowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
ZwCreateFilelowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign

IOCTL dispatch codes (30)

Control codes reachable through the driver dispatch routine. Codes tied to published exploit code are flagged, since they are the primary Bring Your Own Vulnerable Driver (BYOVD) entry points.

CodeSeverityTransferDescription
0x0080BAFFhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #3775
0x0022B807highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #3585
0x00220117highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #69
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x9C4022A0mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #2216
0x9C402454mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #2325
0x9C4026A0mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #2472
0x0080BA00mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #3712
0x9C402A00mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #2688
0x9C402D00mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #2880
0x9C4038FCmediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #3647
0x9C402F94mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #3045
0x9C40354CmediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #3411
0x9C403950mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #3668
0x9C403B38mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #3790
0x9C403D2CmediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #3915
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x0080CB15mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #709
0x0080BC41mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3856
0x0080170DmediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #1475
0x0080EC81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2848
0x00802D00mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2880
0x0080BA41mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3728
0x0080BF41mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #4048

Showing 24 of 30 extracted control codes.

PE sections

Section layout and Shannon entropy. High entropy in a code section is a packing or encryption indicator.

SectionVirtual sizeRaw sizeEntropyFlags
.text0xA5170xA6006.36CODE, EXEC, READ
.rdata0x0FEC0x10005.02IDATA, READ
.data0x12600x0A005.42IDATA, READ, WRITE
.pdata0x05040x06003.88IDATA, READ
INIT0x0B3C0x0C005.6CODE, EXEC, READ, DISCARD
.rsrc0x04580x06002.73IDATA, READ, DISCARD
.reloc0x00240x02000.5IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardEnabled
ASLREnabled
DEPEnabled
Integrity checkNot enforced
Mitigation score100 / 100

MITRE ATT&CK techniques (13)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
T1014RootkitDefense Evasion
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1112Modify RegistryDefense Evasion
T1211Exploitation for Defense EvasionDefense Evasion
T1542.001Pre-OS Boot: System FirmwarePersistence
T1543.003Windows ServicePersistence
T1547.001Registry Run KeysPersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1569.002Service ExecutionExecution
T1601Modify System ImageDefense Evasion
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerMicrosoft Windows Hardware Compatibility Publisher
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Third Party Component CA 2014
Serial3300000074FF3D4A9E7C401E86000000000074
Valid from2025-07-16 20:48 UTC
Valid until2026-07-14 20:48 UTC
Signature validityVerified

Symbolic execution

Engine angr, status completed, 100 paths explored at a maximum depth of 100. Vulnerability classes reached: 1. Exploitable paths: 0.

Frequently asked questions about ArgusMonitor.sys

Is ArgusMonitor.sys safe?

Based on DriverShield static and dynamic analysis, ArgusMonitor.sys shows some suspicious signals and warrants manual review. Its composite risk score is 30/100 (verdict: suspicious). Always validate findings independently before acting.

What is the risk score of ArgusMonitor.sys?

ArgusMonitor.sys has a DriverShield composite risk score of 30/100, placing it in the suspicious verdict band. SHA256: bd62fa2cb145750fd4214f0ca57f3b314303791305e0b971510f796c0ff88247.

What is ArgusMonitor.sys?

ArgusMonitor.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by Microsoft Windows Hardware Compatibility Publisher.

Related: Other drivers signed by Microsoft Windows Hardware Compatibility Publisher · What an IOCTL dispatch code is · BYOVD research index · full driver database · CVE library · code signing atlas


DriverShield © 2025-2026 · Terms · Privacy · Contact