Repository navigation
injection_createremotethread: detect CreateRemoteThreadEx / NtCreateThreadEx by target ProcessId - #609
Open
systems1024github wants to merge 1 commit into
Conversation
…hreadEx by target ProcessId Fixes CAPESandbox#607 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013ZmeuAL8LRvUVBUbjrEu8j
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.
Fixes #607
On Windows 10/11 guests,
injection_createremotethreaddoes not fire on the classic VirtualAllocEx + WriteProcessMemory + CreateRemoteThread injection:CreateRemoteThreadEx, which the exact-name test (== "CreateRemoteThread") misses;NtCreateThreadExis called with a process handle of its own, not the one returned by OpenProcess/NtOpenProcess, so the handle lookup fails too. capemon does log the target'sProcessId.This change accepts
CreateRemoteThreadExand, when the handle is not one the signature saw opened, falls back to the call'sProcessIdif it is one ofself.process_pids. The existing handle path is unchanged.Tested on a Windows 11 guest:
The two PID pairs come from two different runs of the same sample, so they differ.
Checked with
python -m py_compile,black --check,isort --check-onlyand the CI'sflake8 --select=E9,F63,F7,F82.🤖 Generated with Claude Code
https://claude.ai/code/session_013ZmeuAL8LRvUVBUbjrEu8j