amp.sys - Suspicious (45/100) - DriverShield Analysis

Analysis of amp.sys: suspicious verdict, risk score 45/100. 1 YARA match, 1/75 multi-engine detections. SHA256 cbb8239a765bf5b2. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

amp.sys - Analysis Report

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

VerdictSuspicious (45/100)
YARA matches1
Multi-engine detections1 / 75
File size174856 bytes
Code-signing signerSymantec Time Stamping Services CA - G2
Analyzed2026-09-06
SHA256cbb8239a765bf5b2c1b6a5c8832d2cab8fef5deacadfb65d8ed43ef56d291ab6
SHA13f223581409492172a1e875f130f3485b90fbe5f
MD5c533d6d64b474ffc3169a0e0fc0a701a

Driver identity

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

File descriptionAMP Minifilter
ProductCYREN AMP 5
CompanyCYREN Inc.
Original filenameamp.sys
Internal nameAMP
File version5.4.11.1
CopyrightCopyright © 1999 - 2014. CYREN Inc. All rights reserved.

How the 45/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 surface100 / 100
Known-vulnerable corpus100 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (28)

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

APIRiskWhy it matters
ZwOpenProcesshighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
IoGetDeviceObjectPointermediumModerate risk - system modification capability
ZwSetValueKeymediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
ZwSetInformationFilemediumModerate risk - system modification capability
ZwWriteFilemediumModerate risk - system modification capability
ZwCreateKeymediumModerate risk - system modification capability
ZwQueryValueKeylowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
RtlInitAnsiStringlowStandard kernel API - generally benign
ZwCreateFilelowStandard kernel API - generally benign
KeDelayExecutionThreadlowStandard kernel API - generally benign
ZwQueryInformationFilelowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
ExFreePoollowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
ZwReadFilelowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
IoBuildDeviceIoControlRequestlowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
ExAllocatePoollowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign

IOCTL dispatch codes (34)

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
0x0080B883highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #3616
0x0080888BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #546
0x00808D8BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #866
0x0080808BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #34
0x00802494mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2341
0x0022E838mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #2574
0x0080BA4AmediumMETHOD_OUT_DIRECTFILE_DEVICE_CUSTOM Function #3730
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x008024A4mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2345
0x0022E820mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #2568
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343
0x00808389mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #226
0x008024BCmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2351
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x00222424mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #2313
0x00223824mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #3593
0x008087E8mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #506
0x00343024mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #3081
0x00342444mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #2321
0x0022B9F1mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #3708
0x0080B941mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3664
0x0080E905mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2625
0x0080E900mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2624
0x0080C481mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #288

Showing 24 of 34 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
.text0x1F9600x1FA005.79CODE, EXEC, READ
.rdata0x4F900x50004.5IDATA, READ
.data0x2B400x0C002.41IDATA, READ, WRITE
.pdata0x19C80x1A005.26IDATA, READ
INIT0x0F3A0x10004.92CODE, EXEC, READ, WRITE, DISCARD
.rsrc0x04B80x06002.93IDATA, READ, DISCARD
.reloc0x02B60x04002.06IDATA, 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_Cyreninc_Amp_Cyrenamp_CBB8mediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - amp.sys. Investigate matches in context: expected filenames or standard vend...

MITRE ATT&CK techniques (12)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1055.001Process Injection: DLL InjectionDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1071Application Layer ProtocolCommand and Control
T1112Modify RegistryDefense Evasion
T1211Exploitation for Defense EvasionDefense Evasion
T1489Service StopImpact
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

SignerSymantec Time Stamping Services CA - G2
Signer organisationSymantec Corporation
IssuerThawte Timestamping CA
Serial7E93EBFB7CC64E59EA4B9A77D406FC3B
Valid from2012-12-21 00:00 UTC
Valid until2020-12-30 23:59 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 amp.sys

Is amp.sys safe?

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

What is the risk score of amp.sys?

amp.sys has a DriverShield composite risk score of 45/100, placing it in the suspicious verdict band. SHA256: cbb8239a765bf5b2c1b6a5c8832d2cab8fef5deacadfb65d8ed43ef56d291ab6.

What is amp.sys?

amp.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by Symantec Time Stamping Services CA - G2.

Related: Other drivers signed by Symantec Time Stamping Services CA - G2 · 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