Skip to content

feat(rules): New Suspicious registry symbolic link creation rule#684

Open
rabbitstack wants to merge 1 commit into
masterfrom
suspicious-registry-symbolic-link-creation
Open

feat(rules): New Suspicious registry symbolic link creation rule#684
rabbitstack wants to merge 1 commit into
masterfrom
suspicious-registry-symbolic-link-creation

Conversation

@rabbitstack

Copy link
Copy Markdown
Owner

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

Detects the creation of registry symbolic links, a technique that allows attackers to redirect registry key lookups to arbitrary locations within the registry hive. Adversaries abuse this mechanism to manipulate the registry namespace and influence how privileged processes or system services resolve registry paths, potentially enabling privilege escalation without exploiting a traditional code vulnerability.

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?


Detects the creation of registry symbolic links, a technique that
allows attackers to redirect registry key lookups to arbitrary locations within the registry hive.
Adversaries abuse this mechanism to manipulate the registry namespace and influence how privileged processes or system services resolve registry paths, potentially enabling privilege escalation without exploiting a traditional code vulnerability.
@rabbitstack rabbitstack added the rules Anything related to detection rules label Jun 27, 2026
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.

1 participant