Skip to main content
Mallory
← Back to News
detection-content-updateloader-delivery-mechanisminitial-access-methodcommand-and-control-method

Elastic Applies LLM Triage to `curl` and `wget` Ingress Tool Transfer Detections

Patch & Detection Intelligence · 3 sources · Updated 3mo ago · First seen Jul 23, 2026

Elastic Applies LLM Triage to `curl` and `wget` Ingress Tool Transfer Detections

Elastic Security Labs detailed a detection pipeline that uses ES|QL COMPLETION to reduce noise from curl and wget execution alerts tied to MITRE ATT&CK T1105 Ingress Tool Transfer, a technique widely used by threat actors to download second-stage payloads, post-exploitation tools, and ransomware from command-and-control infrastructure. The approach preserves deterministic detections, then extracts destination hosts, applies allow-lists, redacts secrets from command lines, aggregates remaining events, and submits only a small set of high-value records to an LLM for a structured verdict of true positive, false positive, or suspicious.

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.

2 events · Jul 23, 2026
  1. Jul 23, 20264mo ago

    Elastic publishes ES|QL COMPLETION triage approach

    Elastic described a detection-engineering workflow that uses ES|QL COMPLETION to triage noisy curl and wget execution events before they become analyst-facing alerts in cloud environments. The approach preserves deterministic rules, applies destination parsing and allow-listing, redacts secrets, and sends only limited high-value rows to an LLM for structured verdicts.

    ES|QL COMPLETION: LLM triage for noisy detection rules - Elastic Security Labs
  2. Jul 23, 20264mo ago

    Elastic tests ES|QL triage pipeline on wget events

    Elastic ran its wget-focused ES|QL COMPLETION triage pipeline over seven days on its own cloud fleet in June 2026. After deterministic filtering, only three destinations remained, with two classified as false positives and one as suspicious, resulting in no analyst-opened alerts.

    ES|QL COMPLETION: LLM triage for noisy detection rules - Elastic Security Labs
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
Elastic Cloud Serverless

Organizations

1 linked
Elastic
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.