Process Parameter Poisoning and the Limits of EDR Evasion Claims
Meta title: Process Parameter Poisoning and EDR Evasion
OG title: What Process Parameter Poisoning Claims—and What Windows Documents
Description: Dark Reading reports process parameter poisoning as part of a commercial EDR-evasion stack. Here’s what Windows documentation and MITRE ATT&CK establish about process creation and injection—and what remains unverified.
Dark Reading reported process parameter poisoning in coverage of a commercial “EDR evasion stack” associated with process injection. The report makes the subject worth examining, but it is not a technical specification of the tool. To understand the claim, it helps to separate the report from the documented Windows mechanisms and the broader process-injection category. [1][2][3]
The claim in context
Process injection is a broad category: code is made to execute in the address space of another process. MITRE ATT&CK describes process injection as a way to evade process-based defenses and potentially gain access to the target process’s resources. That general description does not establish how the tool discussed by Dark Reading works. [2]
Dark Reading reports process parameter poisoning as part of its discussion of the commercial stack. The report does not provide enough implementation detail to establish which Windows structures the tool changes, where any payload is stored, or when those changes occur. Nor does it establish the tool’s detection rate across endpoint products. Those specifics should not be inferred from the technique’s name. [1]
Windows process creation: what is documented
Windows process creation is a set of documented operations, not a single instant. The CreateProcess family creates a process and its primary thread; the CREATE_SUSPENDED flag allows the primary thread to be created suspended, and ResumeThread can later resume a suspended thread. These documented options describe Windows behavior generally. They do not show that the reported tool uses them. [3][4][5]
The Process Environment Block (PEB) contains process-level information and pointers to other structures. In particular, its Ldr field points to loader-related data, including the loader’s module lists; the loader data structures are not themselves contained in the PEB. The PEB also has a pointer to process parameters. Microsoft cautions that these internal structures may change between Windows versions, so their undocumented details should be treated carefully. [6][7]
This distinction matters when discussing “process parameter poisoning.” The name alone does not identify which parameter or structure is affected, or whether the alleged technique acts before a process’s first execution. Windows documentation supplies useful context about process creation and related structures, but it does not verify the reported tool’s implementation. [1][3][6][7]
How the claim relates to MITRE ATT&CK
MITRE ATT&CK classifies Process Injection (T1055) as a broad technique with multiple sub-techniques, including DLL Injection (T1055.001), Portable Executable Injection (T1055.002), Thread Execution Hijacking (T1055.003), Asynchronous Procedure Call (T1055.004), Process Hollowing (T1055.012), and Process Doppelgänging (T1055.013). The taxonomy describes behaviors; it does not assign a technique based on a vendor’s label. [2]
Process hollowing is one documented process-injection sub-technique, but resemblance in timing or terminology is not enough to classify the reported tool as hollowing, or as any other specific sub-technique. Classification requires evidence about observed behavior. [1][2]
What defenders can reasonably take from this
The report is a reminder to ask what process and memory activity an endpoint product can observe, and when that collection begins. It is not evidence that AI-based detection is necessary, that a particular product will miss the technique, or that any detection approach will catch it. Claims about detection effectiveness require product-specific evidence and testing. [1]
As general defensive practice, correlate process and thread activity with available memory, file, network, and authentication events. Investigate cross-process access in context, since legitimate software such as debuggers and management tools may also interact with other processes. Baseline expected process relationships for your environment, and test detection logic against documented behaviors rather than assuming coverage from a product label. These are broad investigative recommendations, not proven countermeasures to the reported tool. [2][3]
When evaluating a vendor, ask what process, thread, and memory telemetry it collects, when collection starts, and what limitations apply. Validate the answers in your own environment; the report alone cannot establish how a particular sensor performs. [1]
The takeaway
Process parameter poisoning is a reported label associated with an EDR-evasion stack, not a sufficiently documented implementation that can be mapped confidently to a specific Windows mechanism or ATT&CK sub-technique. Windows documentation clarifies the relevant process-creation options and the relationship between the PEB and loader data. For defenders, the practical next step is to evaluate telemetry and detections against observed behavior, without treating the report as proof of a particular technique or outcome. [1][2][3][6][7]
Sources
[1] Dark Reading, “EDR Evasion Stack Helps Process Injection Slip Past Defenses”.
[2] MITRE ATT&CK, T1055: Process Injection.
[3] Microsoft Learn, Process and Thread Functions.
[4] Microsoft Learn, Process Creation Flags.
[5] Microsoft Learn, ResumeThread function.
[6] Microsoft Learn, PEB structure.
[7] Microsoft Learn, PEB_LDR_DATA structure.