Addded rule for LNK Command-Line Padding with Whitespace Characters#5240
Merged
nasbench merged 2 commits intoSigmaHQ:masterfrom Apr 16, 2025
Merged
Addded rule for LNK Command-Line Padding with Whitespace Characters#5240nasbench merged 2 commits intoSigmaHQ:masterfrom
nasbench merged 2 commits intoSigmaHQ:masterfrom
Conversation
github-actions
Bot
added
Rules
Windows
nasbench
approved these changes
Mar 21, 2025
frack113
approved these changes
Mar 21, 2025
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
3 participants
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.
Summary of the Pull Request
Added a rule to detect possible exploitation of ZDI-CAN-25373 as reported by Trendmicro.
According to Trendmicro, ZDI-CAN-25373 relates to the way Windows displays the contents of shortcut (.lnk) files through the Windows UI. By exploiting this vulnerability, an attacker can prepare a malicious .lnk file for delivery to a victim. Upon examining the file using the Windows-provided user interface, the victim will not be able to tell that the file contains any malicious content. The sections below explain the vulnerability in further detail.
Changelog
new: Suspicious LNK Command-Line Padding with Whitespace Characters
Example Log Event
0xa.log
Fixed Issues
SigmaHQ Rule Creation Conventions