Files
splunk-security_content/dev/endpoint/suspicious_curl_network_connection.yml
2023-02-28 12:00:16 +01:00

52 lines
1.5 KiB
YAML

name: Suspicious Curl Network Connection
id: 3f613dc0-21f2-4063-93b1-5d3c15eef22f
version: 1
date: '2021-02-22'
author: Michael Haag, Splunk
status: experimental
type: TTP
description: The following analytic identifies the use of a curl contacting suspicious
remote domains to checkin to Command And Control servers or download further implants.
In the context of Silver Sparrow, curl is identified contacting s3.amazonaws.com.
This particular behavior is common with MacOS adware-malicious software.
data_source:
- Sysmon Event ID 1
search:
selection1:
CommandLine: s3.amazonaws.com
Image|endswith: curl
condition: selection1
how_to_implement: To successfully implement this search you need to be ingesting information
on process that include the name of the process responsible for the changes from
your endpoints into the `Endpoint` datamodel in the `Processes` node.
known_false_positives: Unknown. Filter as needed.
references:
- https://redcanary.com/blog/clipping-silver-sparrows-wings/
- https://www.marcosantadev.com/manage-plist-files-plistbuddy/
tags:
analytic_story:
- Silver Sparrow
- Ingress Tool Transfer
- Linux Living Off The Land
asset_type: Endpoint
confidence: 50
impact: 50
message: tbd
mitre_attack_id:
- T1105
observable:
- name: user
type: User
role:
- Victim
- name: dest
type: Hostname
role:
- Victim
product:
- Splunk Enterprise
- Splunk Enterprise Security
- Splunk Cloud
risk_score: 25
security_domain: endpoint