dma-attack-techniques

Develop PCIe DMA threat models and detection-oriented mitigation plans for game security.

69|11|Updated May 16, 2026
One-click install
npx skills add https://github.com/NeverSight/NeverC --skill dma-attack-techniques-neversight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dma-attack-techniques
Source: https://github.com/NeverSight/NeverC/tree/main/.agents/skills/dma-attack-techniques
Command: npx skills add https://github.com/NeverSight/NeverC --skill dma-attack-techniques-neversight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you systematically understand how external PCIe DMA cheats can read or influence a game below the OS, and what observables and mitigation limits matter when an attacker can act as an untrusted device.

Core Features & Use Cases

  • PCIe DMA threat modeling: covers external DMA cheat architecture (FPGA PCIe endpoint, TLP flow, and optional HID actuator) and explains the “no attacker code executes on the gaming PC” property.
  • Protocol-level fingerprinting guidance: breaks down TLP/DLLP/physical-layer behaviors, including TLP header fields, tag discipline, MPS/MRRS negotiation, completion splitting patterns, LTSSM/ASPM signals, and config-space capability chains that can be used for detection.
  • Defense layering for anti-cheat: evaluates three defense layers (PCIe-level fingerprinting, IOMMU enforcement, and measured attestation) and maps specific Windows security features and IOMMU concepts (IOTLB, ATS, PASID, ACS, interrupt remapping) to practical defensive implications.

Quick Start

Use the dma-attack-techniques skill to produce a PCIe DMA threat model and a prioritized mitigation plan for anti-cheat detection focusing on IOMMU, ATS trust, ACS/P2P paths, and configuration space fingerprint checks.

Frequently Asked Questions about dma-attack-techniques

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do PCIe DMA cheats read game memory without executing code on the gaming PC?

PCIe DMA cheats use an external FPGA PCIe endpoint to send TLPs directly to system memory, bypassing the OS entirely. This external device architecture ensures no attacker code executes on the gaming PC, reading memory below the operating system level via direct hardware access.

What PCIe configuration space fingerprints can anti-cheat systems use for DMA detection?

PCIe configuration fingerprint validation checks TLP header fields, tag discipline, MPS/MRRS negotiation, completion splitting patterns, LTSSM/ASPM signals, and capability chains. These protocol-level observables identify untrusted external devices attempting DMA attacks through hardware behavior anomalies.

How do I model IOMMU and VT-d isolation to mitigate external DMA attacks?

Model IOMMU enforcement by mapping IOTLB, ATS, PASID, and interrupt remapping to defensive controls. Evaluate ATS untrusted mode, ACS enforcement for P2P paths, and IOMMU fault signaling to constrain DMA access and detect unauthorized memory reads from external PCIe devices.

Does ACS enforcement help block DMA cheats using pcileech workflows?

ACS enforcement blocks unauthorized peer-to-peer DMA paths, preventing direct memory access between devices. It complements IOMMU fault signaling and PCIe configuration fingerprint validation to detect pcileech workflows and constrain external FPGA devices acting as untrusted PCIe endpoints.

What are the limitations of firmware mimicry and device impersonation in DMA attacks?

Device impersonation and firmware mimicry limit detection by emulating legitimate PCIe endpoint behaviors. However, physical-layer LTSSM/ASPM signals, TLP tag discipline, and completion splitting patterns remain observable, allowing anti-cheat systems to identify untrusted devices through protocol-level fingerprinting despite firmware spoofing.

Can I use measured attestation alongside PCIe fingerprinting for layered anti-cheat defense?

Measured attestation provides a third defense layer alongside PCIe-level fingerprinting and IOMMU enforcement. By validating device integrity, it detects firmware mimicry and device impersonation, mapping protocol observables to defensive controls for comprehensive DMA threat mitigation in game security scenarios.