Skip to main content
Mallory
← Back to News
detection-content-updatewidely-deployed-product-advisoryprivilege-escalation-methoddata-exfiltration-method

Splunk Retires MLTK Detections for Risky SPL Command Abuse After Vulnerability Patches

Patch & Detection Intelligence · 5 sources · Updated 3mo ago · First seen May 14, 2026

Splunk Retires MLTK Detections for Risky SPL Command Abuse After Vulnerability Patches

Splunk has removed several Enterprise Security detections that were built to identify abuse of risky Search Processing Language (SPL) commands, including "Splunk Command and Scripting Interpreter Risky SPL MLTK", "Detect Risky SPL using Pretrained ML Model", and "Splunk risky Command Abuse disclosed february 2023". The analytics monitored Splunk_Audit.Search_Activity data for ad hoc searches using commands such as collect, delete, fit, outputcsv, outputlookup, run, script, sendalert, sendemail, and tscollect, which could be abused to bypass warnings, escalate privileges, delete data, exfiltrate information, or support arbitrary code execution and persistence. Splunk said the detections were disabled by default and mapped to ATT&CK techniques including T1059, T1202, and T1548.

The retired content relied on the Machine Learning Toolkit (MLTK) and, in some cases, pretrained models or per-user baselines to flag anomalous long-running risky searches or suspicious command text. Splunk originally promoted the approach as a way to complement rule-based detections for exploitation tied to CVE-2022-32154 and later risky-command vulnerabilities, but the company has since withdrawn the analytics from its Threat Research library because the affected flaws have been patched in current Splunk releases. Splunk also noted operational drawbacks, including false positives from legitimate long-running searches and added compute requirements for model training in larger environments.

Patch this, or something else?See real exploitation activity before you spend the cycle.
Triage this advisory
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

4 events · Jul 26, 2022 – May 14, 2026
  1. May 14, 20266mo ago

    Splunk removes pretrained ML risky SPL detection

    Splunk Threat Research removed the detection "Detect Risky SPL using Pretrained ML Model" from its content library and said it was no longer maintained because the associated CVEs had been patched in the latest Splunk release. The analytic had used a pretrained text classifier to score ad hoc SPL activity for suspicious risky commands.

    Detection: Detect Risky SPL using Pretrained ML Model | Splunk Security Content
  2. May 14, 20266mo ago

    Splunk removes Risky SPL MLTK anomaly detection

    Splunk Threat Research removed the detection "Splunk Command and Scripting Interpreter Risky SPL MLTK" in content library version 5.12.0 and said it was no longer maintained or supported. Splunk explained the detection was deprecated because it monitored regular Splunk commands that are not recommended to be used as a detection search.

    Detection: Splunk Command and Scripting Interpreter Risky SPL MLTK | Splunk Security Content
  3. May 14, 20266mo ago

    Splunk removes risky command abuse hunting detection from content library

    Splunk Threat Research removed the detection "Splunk risky Command Abuse disclosed february 2023" from its content library, stating the associated CVEs had been patched in the latest Splunk release. The removed hunting analytic had targeted execution of high-risk commands tied to multiple Splunk vulnerability disclosures.

    Detection: Splunk risky Command Abuse disclosed february 2023 | Splunk Security Content
  4. Jul 26, 20224y ago

    Splunk publishes blog on ML detection of risky SPL command abuse

    Splunk described an anomaly-detection approach for identifying abuse of risky SPL commands using audit log data and the Machine Learning Toolkit's DensityFunction algorithm. The blog said the corresponding ESCU detection was named "Splunk Command and Scripting Interpreter Risky SPL MLTK" and reported successful testing with implanted anomalies.

    ML Detection of Risky Command Exploit | Splunk
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Affected products

1 linked
Splunk Enterprise

Organizations

1 linked
Splunk
Do you run this?See real exploitation activity behind this advisory so you can triage it against everything else in the queue.
Prioritize This Patch
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.