Skip to content

Double the lone backslashes in the path patterns of six detections - #4426

Open
TT5H wants to merge 1 commit into
splunk:developfrom
TT5H:fix-lone-backslashes-in-path-patterns
Open

TT5H wants to merge 1 commit into
splunk:developfrom
TT5H:fix-lone-backslashes-in-path-patterns

Conversation

@TT5H

@TT5H TT5H commented Nov 16, 2026

Copy link
Copy Markdown
Contributor

Fixes #4417.

Details

In tstats and search patterns, Splunk drops a single backslash before an ordinary character, so *\Microsoft\Windows\EventLog\* behaves like *MicrosoftWindowsEventLog*. Six detections have a pattern written that way next to correctly doubled ones. This change doubles the lone backslashes and bumps version and modification_date. Nothing else changes.

I tested in Splunk Enterprise 9.3.14 (Splunk_SA_CIM 6.4.0, Splunk_TA_windows 9.1.2, Splunk_TA_microsoft_sysmon 5.0.0). I ran the published search and the fixed search on the test recording of each detection, and on a copy of one recorded event with a single field changed ("changed event"). A changed event that matches a correctly written pattern gave the same result in both versions.

Detection Pattern Published search Fixed search
Windows New EventLog ChannelAccess Registry Value Set *\Microsoft\Windows\EventLog\* test recording: returns 2 of 3 ChannelAccess events, not the Policies\...\EventLog\Setup value returns all 3
Windows Known Abused DLL Created *\\Windows\Temp\\* changed event C:\Windows\Temp\version.dll: not returned returned. Checked up to the tstats part, because my instance had no hijacklibs_loaded lookup
Windows Defender MpClient.dll Loaded by Non-Defender Process *\MpCmdRun.exe changed event C:\Users\Administrator\Desktop\fakeMpCmdRun.exe: not returned, as if it were MpCmdRun.exe returned
Windows Unusual Process Load Mozilla NSS-Mozglue Module 3 patterns (Program Files\Mozilla Firefox, Program Files (x86)\Mozilla Firefox, Cyberfox\cyberfox.exe) changed events with those three default paths: returned, not excluded not returned
Windows Unusual FileZilla XML Config Access C:\Program Files (x86)\\FileZilla FTP Client\\filezilla.exe changed event with that path: returned, not excluded not returned
Windows Snake Malware Service Create *\Werfault.exe same result on the test recording. It also returns a changed event ...\evilWerFault.exe does not return it

I left out Registry Keys Used For Persistence, which has the same lone backslash in \CurrentControlSet\Control\Session Manager. Its condition registry_key_name="BootExecute" cannot match Sysmon data either way: the data model puts BootExecute in registry_value_name.

A scan of all 2,213 detection searches for a single backslash before a letter in a path pattern, outside regular expressions, found no other file.

I left the other checklist items open. Each file changes only version, modification_date and one search line, and CI has not run yet.

Checklist

  • Validate name matches <platform>_<mitre att&ck technique>_<short description> nomenclature
  • CI/CD jobs passed ✔️
  • Validated SPL logic.
  • Validated tags, description, and how to implement.
  • Verified references match analytic.
  • Confirm updates to lookups are handled properly.

Notes For Submitters and Reviewers

  • If you're submitting a PR from a fork, ensuring the box to allow updates from maintainers is checked will help speed up the process of getting it merged.
  • Checking the output of the build CI job when it fails will likely show an error about what is failing. You may have a very descriptive error of the specific field(s) in the specific file(s) that is causing an issue. In some cases, its also possible there is an issue with the YAML. Many of these can be caught with the pre-commit hooks if you set them up. These errors will be less descriptive as to what exactly is wrong, but will give you a column and row position in a specific file where the YAML processing breaks. If you're having trouble with this, feel free to add a comment to your PR tagging one of the maintainers and we'll be happy to help troubleshoot it.
  • Updates to existing lookup files can be tricky, because of how Splunk handles application updates and the differences between existing lookup files being updated vs new lookups. You can read more here but the short version is that any changes to lookup files need to bump the the date and version in the associated YAML file.

Splunk drops a single backslash before an ordinary character in tstats and
search patterns, so these patterns did not match the paths they name. Double
them as in the neighbouring patterns, bump the version of each detection and
set its modification date.

Fixes splunk#4417

@Varunpoojari Varunpoojari left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for taking this on and for testing each one in Splunk, the table makes the effect of every change clear.

I read the diff: each file only doubles the lone backslashes and bumps version and modification_date. The #4417 line is identical to the fix I had made locally, and the other five match the patterns I'd flagged. Good call leaving out Registry Keys Used For Persistence; I'll look at the registry_key_name / registry_value_name issue there separately.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] Windows New EventLog ChannelAccess Registry Value Set: second path has single backslashes

2 participants