Add SystemSettingsAdminFlows.exe - #518
Open
ashish-cybersec wants to merge 3 commits into
Open
Conversation
Removed Code_Sample section from SystemSettingsAdminFlows.yml.
Updated detection rules and analysis links for SystemSettingsAdminFlows.
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
1 participant
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.
Adds an OSBinaries entry for SystemSettingsAdminFlows.exe, the Settings app's
elevation helper, documenting four Defender configuration flows that are
invokable directly from the command line.
On the criteria. The unexpected functionality here isn't that the binary
changes Defender settings — it's that those flows are reachable as command-line
arguments from any elevated process, entirely outside the Settings UI and its
confirmation path. Notably, this route touches neither Set-MpPreference nor a
direct registry write, which is where most existing Defender-tamper detections
are anchored. Categorised as Tamper per CategoryList.md, mapped to T1562.001.
Observed in the wild by two independent reporters:
https://thedfirreport.com/2026/02/23/apache-activemq-exploit-leads-to-lockbit-ransomware/
Detection. Process-creation and Defender Operational IOCs, plus the SigmaHQ
rule written for this technique (da92713f-ca2d-4fab-8320-098013d3f43a), which
cites the same two sources.
The entry covers the four arguments reported in those two intrusions. The Sigma
rule additionally matches
RealTimeProtectionandDisableCDPUserAuthPolicy—happy to fold those in if you'd prefer fuller coverage.
Passes validation.py and .yamllint locally. First submission, so please tell me
what to fix.