Skip to content

Fixed non-escaped double quotes on PowerShell_DLL_List.mkape#1103

Merged
AndrewRathbun merged 1 commit into
EricZimmerman:masterfrom
JorZay:master
Apr 21, 2026
Merged

Fixed non-escaped double quotes on PowerShell_DLL_List.mkape#1103
AndrewRathbun merged 1 commit into
EricZimmerman:masterfrom
JorZay:master

Conversation

@JorZay
Copy link
Copy Markdown
Contributor

@JorZay JorZay commented Apr 21, 2026

Non-escaped double-quotes were preventing the module from properly executing:
" Modules : The term 'Modules' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:36 + gps | Format-List ProcessName, @{l=Modules;e={$_.Modules|Out-String}} + ~~~~~~~ + CategoryInfo : ObjectNotFound: (Modules:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException "

Description

Please include a summary of the change and (if applicable) which issue is fixed.

Checklist:

Please replace every instance of [ ] with [X] OR click on the checkboxes after you submit your PR

  • I have generated a unique GUID for my Target(s)/Module(s)
  • I have placed the Target(s)/Module(s) in an appropriate subfolder in Targets or Modules. If one doesn't exist, I have either added it to the Misc folder or created a relevant subfolder with justification
  • I have set or updated the version of my Target(s)/Module(s)
  • I have verified that KAPE parses the Target(s)/Module(s) successfully via kape.exe, using --tlist/--mlist and corrected any errors
  • I have validated my Target(s)/Module(s) against test data and verified they are working as intended
  • I have made an attempt to document the artifacts within the Target(s) or Module(s) I am submitting. If documentation doesn't exist, I have placed N/A underneath the Documentation header
  • For Targets, I have consulted either the Target Guide, Target Template, Compound Target Guide, or Compound Target Template to ensure my Target(s) follow the same format
  • For Modules, I have consulted either the Module Guide, Module Template, Compound Module Guide, or Compound Module Template to ensure my Module(s) follow the same format

If your submission involves an SQLite database, have you considered making an SQLECmd Map for the SQLite database? If you make a Map, please add the SQLite database to the SQLiteDatabases.tkape Compound Target.

Thank you for your submission and for contributing to the DFIR community!

Non-escaped double-quotes were preventing the module from properly executing:
" Modules : The term 'Modules' is not recognized as the name of a cmdlet, function, script file, or operable program.     Check the spelling of the name, or if a path was included, verify that the path is correct and try again.               At line:1 char:36                                                                                                       + gps | Format-List ProcessName, @{l=Modules;e={$_.Modules|Out-String}}                                                 +                                    ~~~~~~~                                                                                + CategoryInfo          : ObjectNotFound: (Modules:String) [], CommandNotFoundException                                 + FullyQualifiedErrorId : CommandNotFoundException                                                                                                                                     "
@JorZay JorZay changed the title Fixed non-escaped double quotes Fixed non-escaped double quotes on PowerShell_DLL_List.mkape Apr 21, 2026
@AndrewRathbun AndrewRathbun self-assigned this Apr 21, 2026
@AndrewRathbun AndrewRathbun added the bug Something isn't working label Apr 21, 2026
@AndrewRathbun AndrewRathbun merged commit 7304321 into EricZimmerman:master Apr 21, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants