Suspicious LNK Command-Line Padding with Whitespace Characters

Title: Suspicious LNK Command-Line Padding with Whitespace Characters
Status: experimental
Description:Detects exploitation of LNK file command-line length discrepancy, where attackers hide malicious commands beyond the 260-character UI limit while the actual command-line argument field supports 4096 characters using whitespace padding (e.g., 0x20, 0x09-0x0D). Adversaries insert non-printable whitespace characters (e.g., Line Feed \x0A, Carriage Return \x0D) to pad the visible section of the LNK file, pushing malicious commands past the UI-visible boundary. The hidden payload, executed at runtime but invisible in Windows Explorer properties, enables stealthy execution and evasion—commonly used for social engineering attacks. This rule flags suspicious use of such padding observed in real-world attacks.
References:
  -https://syedhasan010.medium.com/forensics-analysis-of-an-lnk-file-da68a98b8415
  -https://thehackernews.com/2025/03/unpatched-windows-zero-day-flaw.html
  -https://www.trendmicro.com/en_us/research/25/c/windows-shortcut-zero-day-exploit.html
Author: Swachchhanda Shrawan Poudel (Nextron Systems)
Date: 2025-03-19
modified:None
Tags:

• -'attack.initial-access'
• -'attack.execution'
• -'attack.t1204.002'

Logsource:

• category: process_creation
• product: windows

Detection:
  selection_img:
ParentImage|endswith:'\explorer.exe' ParentCommandLine|contains:'.lnk'   selection_cmd:
    - CommandLine|contains:
      - ' '
      - '\u0009'
      - '\u000A'
      - '\u0011'
      - '\u0012'
      - '\u0013'
      - '\u000B'
      - '\u000C'
      - '\u000D'
CommandLine|re:'\n\n\n\n\n\n'   condition:all of selection_*
Falsepositives:
  -Unknown
Level: high