Skip to content

Conversation

@rabbitstack
Copy link
Owner

What is the purpose of this PR / why it is needed?

Detects the execution of a process clone via RtlCreateProcessReflection followed by network activity or loading of common networking DLLs. This behaviour may indicate that an attacker is abusing process reflection for shellcode injection.

What type of change does this PR introduce?


Uncomment one or more /kind <> lines:

/kind feature (non-breaking change which adds functionality)

/kind bug-fix (non-breaking change which fixes an issue)

/kind refactor (non-breaking change that restructures the code, while not changing the original functionality)

/kind breaking (fix or feature that would cause existing functionality to not work as expected

/kind cleanup

/kind improvement

/kind design

/kind documentation

/kind other (change that doesn't pertain to any of the above categories)

Any specific area of the project related to this PR?


Uncomment one or more /area <> lines:

/area instrumentation

/area telemetry

/area rule-engine

/area filters

/area yara

/area event

/area captures

/area alertsenders

/area outputs

/area rules

/area filaments

/area config

/area cli

/area tests

/area ci

/area build

/area docs

/area deps

/area evasion

/area other

Special notes for the reviewer


Does this PR introduce a user-facing change?


@rabbitstack rabbitstack added the rules Anything related to detection rules label Feb 3, 2026
Detects the execution of a process clone via RtlCreateProcessReflection followed by network activity or loading of common networking DLLs.
This behaviour may indicate that an attacker is abusing process reflection for shellcode injection.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

rules Anything related to detection rules

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants