dma-attack-techniques
Guide for PCIe DMA threat modeling, FPGA-based memory access, and defensive implications in game security. Use this skill when researching pcileech, BAR and TLP behavior, page-table walking, IOMMU or VT-d, device impersonation, firmware mimicry, or DMA detection and mitigation in game security research.
56
63%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Critical
Do not install without reviewing
Fix and improve this skill with Tessl
tessl review fix ./.claude/skills/dma-attack/SKILL.mdSecurity
2 findings: 1 critical severity, 1 medium severity. Installing this skill is not recommended: please review these findings carefully if you do intend to do so.
E006: Malicious code pattern detected in skill scripts.
What this means
Detected high-risk code patterns in the skill content — including its prompts, tool definitions, and resources — such as data exfiltration, backdoors, remote code execution, credential theft, system compromise, supply chain attacks, and obfuscation techniques.
Why it was flagged
This document provides explicit, actionable techniques and tooling (pcileech, MemProcFS, DMA card/actuator architecture, IOMMU bypasses, shadow CR3/EPT manipulation, and archive URLs to fetch attack code) for unauthorized physical-memory access, data exfiltration, input injection, and stealthy persistence—clearly facilitating deliberate malicious abuse.
W013: Attempt to modify system services in skill instructions.
What this means
The skill prompts the agent to compromise the security or integrity of the user’s machine by modifying system-level services or configurations, such as obtaining elevated privileges, altering startup scripts, or changing system-wide settings.
Why it was flagged
The skill contains explicit, privileged instructions to reprogram IOMMU domains, clear Bus Master Enable, access/mount physical memory, and perform direct ECAM/PCI config writes (e.g., BAR probing, Command[BME] toggles, pcileech physical reads), which are actions that modify kernel/hardware state and can compromise the host.
Low
Low-risk findings.
2 low severity findings. Worth noting, but not necessarily harmful.
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
The required workflow includes fetching external GitHub “README/archive/description” content at runtime (outsider-authored free text from public web sources), which would be ingested into the agent’s LLM context when the skill uses that fetched material.
W012: Unverifiable external dependency detected (runtime URL that controls agent).
What this means
The skill fetches instructions or code from an external URL at runtime, and the fetched content directly controls the agent’s prompts or executes code. This dynamic dependency allows the external source to modify the agent’s behavior without any changes to the skill itself.
Why it was flagged
This skill explicitly instructs the agent to fetch and use raw GitHub content at runtime (e.g., https://raw.githubusercontent.com/gmh5225/awesome-game-security/refs/heads/main/README.md), so remote files would be retrieved and injected into the agent's responses, directly controlling prompt/context.
- Repository
- gmh5225/awesome-game-security
- Commit
9efdfd0
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.