libnicm.sys - Suspicious (58/100) - DriverShield Analysis

Analysis of libnicm.sys: suspicious verdict, risk score 58/100. 1 YARA match, 1/76 multi-engine detections. SHA256 95d50c69cdbf10c9. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

libnicm.sys - Analysis Report

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

VerdictSuspicious (58/100)
YARA matches1
Multi-engine detections1 / 76
File size35344 bytes
Code-signing signerMicrosoft Windows Hardware Compatibility Publisher
Analyzed2026-09-06
SHA25695d50c69cdbf10c9c9d61e64fe864ac91e6f6caa637d128eb20e1d3510e776d3
SHA125d812a5ece19ea375178ef9d60415841087726e
MD5c1fce7aac4e9dd7a730997e2979fa1e2

Driver identity

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

File descriptionXTier COM Services Driver
ProductMicro Focus XTier
CompanyMicro Focus
Original filenamelibnicm.sys
File version3.1.12.0
Copyright(C) Copyright 2000-2017, Micro Focus. All Rights Reserved.

How the 58/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 matches5 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface33 / 100
Known-vulnerable corpus100 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (26)

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

APIRiskWhy it matters
MmMapLockedPagesSpecifyCachecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ZwSetValueKeymediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
ZwCreateKeymediumModerate risk - system modification capability
ZwQuerySystemInformationmediumModerate risk - system modification capability
IoDeleteDevicelowStandard kernel API - generally benign
DbgPrintExlowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
RtlInitAnsiStringlowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
KeDelayExecutionThreadlowStandard kernel API - generally benign
ZwCreateFilelowStandard kernel API - generally benign
DbgPrintlowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
ProbeForWritelowStandard kernel API - generally benign
ZwQueryInformationFilelowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
ZwReadFilelowStandard kernel API - generally benign
ProbeForReadlowStandard kernel API - generally benign
ZwOpenFilelowStandard kernel API - generally benign

IOCTL dispatch codes (11)

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
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343
0x00345715mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #1477
0x00345F15mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #1989
0x00346315mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #2245
0x008024BCmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2351
0x0034DB0DmediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #1731
0x00344B0DmediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #707
0x0080C481mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #288
0x00220020mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #8
0x003402F8mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #190

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x3B200x3C006.27CODE, EXEC, READ
.rdata0x05840x06004.44IDATA, READ
.data0x09680x04002.77IDATA, READ, WRITE
.pdata0x02340x04002.56IDATA, READ
.edata0x018E0x02004.12IDATA, READ
INIT0x0B4C0x0C005.58CODE, EXEC, READ, WRITE, DISCARD
.rsrc0x03580x04002.88IDATA, READ, DISCARD
.reloc0x00180x02000.12IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardNot enabled
ASLRNot enabled
DEPNot enabled
Integrity checkNot enforced
Mitigation score5 / 100

YARA rule matches (1)

RuleSeverityDetects
PUA_VULN_Driver_Microfocus_Microfocusxtier_95D5mediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - libnicm.sys. Investigate matches in context: expected filenames or standard ...

MITRE ATT&CK techniques (12)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1071Application Layer ProtocolCommand and Control
T1112Modify RegistryDefense Evasion
T1211Exploitation for Defense EvasionDefense Evasion
T1543.003Windows ServicePersistence
T1547.001Registry Run KeysPersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1562.001Impair DefensesDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerMicrosoft Windows Hardware Compatibility Publisher
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Third Party Component CA 2014
Serial330000004DE597A775E3157F7B00000000004D
Valid from2021-09-09 19:15 UTC
Valid until2022-09-01 19:15 UTC (expired)
Signature validityNot verified

Symbolic execution

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

Corpus match: this hash is present in the known-vulnerable driver corpus DriverShield cross-references during analysis, which is why the score carries a full weighting on that component.

Frequently asked questions about libnicm.sys

Is libnicm.sys safe?

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

What is the risk score of libnicm.sys?

libnicm.sys has a DriverShield composite risk score of 58/100, placing it in the suspicious verdict band. SHA256: 95d50c69cdbf10c9c9d61e64fe864ac91e6f6caa637d128eb20e1d3510e776d3.

What is libnicm.sys?

libnicm.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 · How YARA matching feeds the score · BYOVD research index · full driver database · CVE library · code signing atlas


DriverShield © 2025-2026 · Terms · Privacy · Contact