<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>TeamTNT - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/actors/teamtnt/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Mon, 12 Oct 2026 17:50:13 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/actors/teamtnt/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>Detection of AWS Credential Exfiltration via Linux Curl</title><link>https://feed.craftedsignal.io/briefs/2026-10-linux-curl-aws-exfil/</link><pubDate>Mon, 12 Oct 2026 17:50:13 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-10-linux-curl-aws-exfil/</guid><description>The TeamTNT threat group leverages the curl utility to exfiltrate sensitive AWS credential and configuration files to remote attacker-controlled servers.</description><content:encoded><![CDATA[<p>Security research indicates that the threat group known as TeamTNT actively exploits legitimate Linux binaries to exfiltrate sensitive cloud configuration data. Specifically, attackers use the curl utility to upload AWS credentials (<del>/.aws/credentials) and configuration files (</del>/.aws/config) to remote destinations. This technique relies on curl's form-based or direct file upload switches, such as -F, --upload-file, or -T. By exfiltrating these files, the actor gains unauthorized access to the victim's AWS environment, potentially leading to resource theft, crypto-mining deployment, or further network lateral movement. Defenders should monitor process command-line arguments for the combination of curl upload flags and sensitive path references.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker gains initial shell access to a Linux-based cloud instance or container.</li>
<li>Attacker performs local reconnaissance to locate cloud credentials, typically in ~/.aws/credentials or ~/.aws/config.</li>
<li>Attacker identifies the availability of the curl binary on the compromised system.</li>
<li>Attacker constructs a malicious curl command utilizing upload switches (-F, --form, -T, or --upload-file) targeting the identified credential files.</li>
<li>Attacker executes the curl command, directing the POST request to an attacker-controlled remote endpoint.</li>
<li>Exfiltrated credentials are received by the attacker's server, enabling cloud resource hijacking.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exfiltration allows for the full compromise of the victim's AWS environment. This exposes the organization to data theft, unauthorized API access, and the deployment of compute-intensive workloads such as cryptominers, which can lead to significant financial costs and infrastructure instability.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the provided Sigma rule to detect curl executions involving sensitive AWS file paths.</li>
<li>Enable comprehensive Sysmon for Linux (Event ID 1) or equivalent EDR process-creation telemetry to ensure visibility into command-line arguments.</li>
<li>Configure alerting for all outbound curl traffic to non-authorized domains from cloud-resident Linux hosts.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">threat</category><category>exfiltration</category><category>linux</category><category>aws</category><category>living-off-the-land</category></item></channel></rss>