Process Parameter Poisoning#2478
Open
carlospolop wants to merge 1 commit into
Open
Conversation
Collaborator
Author
🔗 Additional ContextOriginal Blog Post: https://sensepost.com/blog/2026/process-parameter-poisoning Content Categories: Based on the analysis, this content was categorized under "Windows Hardening > Antivirus (AV) Bypass / Windows Process Injection - add a page for Process Parameter Poisoning (P3)". Repository Maintenance:
Review Notes:
Bot Version: HackTricks News Bot v1.0 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 Automated Content Update
This PR was automatically generated by the HackTricks News Bot based on a technical blog post.
📝 Source Information
🎯 Content Summary
The blog introduces Process Parameter Poisoning (P3), a Windows process-injection and EDR-evasion technique developed by SensePost/Orange Cyberdefense. Instead of transferring payload bytes into a remote process with the classic
VirtualAllocEx+WriteProcessMemorypattern, P3 abuses normal Windows process-creation behavior: attacker-controlled startup parameters passed toCreateProcessWare copied by Windows into the child pr...🔧 Technical Details
Process-parameter shellcode transfer: Instead of using
VirtualAllocExandWriteProcessMemoryto place bytes in a remote process, an attacker can put a payload into parameters that Windows naturally copies duringCreateProcessW. Useful carriers arelpCommandLine,lpEnvironmentwithCREATE_UNICODE_ENVIRONMENT, andSTARTUPINFO.lpReserved, which maps toRTL_USER_PROCESS_PARAMETERS.ShellInfo. After creation, the attacker queriesPROCESS_BASIC_INFORMATIONwithNtQueryInformationProcess, reads the childPEB, followsPEB.ProcessParameters, and obtains pointers toCommandLine,Environment, orShellInfo. This turns normal process creation into a covert payload-transfer mechanism.Execution through thread-context manipulation: Once the copied payload address is known, the attacker c...
🤖 Agent Actions
Plan re-initialized and current state re-verified.
Confirmed:
src/windows-hardening/av-bypass.mdNo final answer yet.
This PR was automatically created by the HackTricks Feed Bot. Please review the changes carefully before merging.