An open project, a commercial ecosystem built on it
pcileech is a research and forensics toolset. Its value is that it documents the PCIe endpoint implementation openly, which is why third parties can build cards around it. The commercial ecosystem layered on top is not part of the project and makes claims the project does not.
01
What pcileech actually provides
The project provides two halves: FPGA firmware that turns a development board into a PCIe bus master, and a host-side client that can issue memory reads and writes against a target system over an external link. It was built for memory forensics — acquiring RAM from a system without booting an acquisition OS.
That origin explains the design. The tooling assumes you control both ends, that the target is your own machine or one you are authorised to examine, and that the goal is evidence rather than interaction with a running application.
02
Firmware variants and what "compatible" means
The project ships several firmware variants targeting different FPGA boards and different emulation goals. Some present as minimal PCIe endpoints; others emulate specific device classes. The variant determines what the target operating system sees during enumeration.
When a retail card says "pcileech compatible", it usually means the vendor adapted one of these variants to their own PCB and maintains that adaptation. Whether they maintain it going forward is a separate question the phrase does not answer.
| Claim | What it usually means | What to verify |
|---|---|---|
| pcileech compatible | Firmware derived from the project | Who maintains the fork, and when last updated |
| Custom firmware | Written in-house or heavily modified | Release history and rollback path |
| Emulates a real device | Class-code and identity emulation | Which device, and why that choice |
03
Limits the project itself documents
Reading memory across a PCIe bus is slow relative to on-die access. Transfer is limited by the external link, and the host client has to issue individual transactions. Throughput figures quoted by vendors describe a specific mode under specific conditions, not a general capability.
The project also assumes an IOMMU that is either disabled or permissive. With VT-d or AMD-Vi enforcing mappings, a bus master cannot reach arbitrary physical addresses, and the firmware has no way around that by design — it is a hardware constraint, not a software one.
- Throughput is bounded by the external link, not the PCIe bus.
- An enforcing IOMMU blocks arbitrary physical addressing by design.
- The toolset targets forensics workflows, not interactive use.
04
Where this is legitimately used
Memory forensics on systems you own or are contracted to examine is the primary legitimate use. Capturing RAM from a machine that will not boot, or from one where a software acquisition agent cannot be installed, is a real problem the tool solves.
Driver and firmware development is the second: having a device that can issue arbitrary bus-master transactions is useful for testing how an operating system handles malformed or unexpected endpoints.
Using the same capability to read another application's memory in a context governed by a Terms of Service is not covered by either use case, and the project's own documentation does not present it as such.
05
Practical risks for buyers
A card running an unmaintained fork of an open project has an unknown failure surface: the vendor may have modified enumeration behaviour without documenting it, and there may be no path back to a known-good firmware if something breaks.
Ask for the firmware version string and the date it was built before purchasing. A vendor who cannot produce that is selling a board with an unknown configuration.
FAQ
Frequently asked questions
01What is pcileech?
An open-source project that implements PCIe bus-mastering from an FPGA plus a host-side client. It was built for memory forensics and documents its own PCIe endpoint implementation openly.
02Does "pcileech compatible" mean the card is good?
It means the vendor adapted firmware derived from the project. It says nothing about whether they maintain that fork, which is the question that actually determines longevity.
03Does pcileech work with an IOMMU enabled?
Not for arbitrary physical addressing. An enforcing IOMMU restricts a bus master to memory the OS has mapped for it, which is a hardware constraint the firmware cannot bypass.
04Is pcileech legal to use?
The project is an open research toolset. Legality depends on what you do with it and where; using it on systems you own or are authorised to examine is the documented use case.
SOURCES
