ARTC2 is a modern execution framework that helps security teams scale attack scenario execution from single and multi-breach point targets. It intends to produce actionable attack intel that improves the effecti of security products and incident response.
ARTC2 Core features and capabilities are sourced from SILENTTRINITY, and atomic tests executed through Boo are from ATOMIC-RED-TEAM. All other feature enhancements were built to ensure operational trade-craft, agility, scalability, and rapid execution are not compromised.
| CAPABILITY | DESCRIPTION |
| ------ | ------ |
| Rapid Deployment | Automate and scale testing efforts from single and multi-target breach points located in different regional en
| Modern Command & Control | *Implant and Ser:* Uses SILENTRINITY's ECDHE Encrypted C2 Communication capabilities to encrypt C2 traffic o. </br>*Client and Ser*: Uses Asyncio, WebSockets, and a prompt-toolkit CLI. Notable features include: *- Implant location tagging: Helpful when managing signals and breakpoints in different regions. NGROK integration* - Great for staging payloads and deploying them with ngrok URLs
| Standard Signature Header | JSON PID: , Date(UTC), IsHighIntegrity, HostName, CurrentUser , IsUserAdmin, IPv4, IPv6
| JSON Logging Support | Streamline, ingest, decode, and analyze e with your ELK stack or any Analytics platform ready to parse JSON.|
||
| Stageless in Memory Code Execution | Execute Atomic Red Team tests from an unmanaged PowerShell process with low, medium, and high integrity.
| Dynamic Attack Formations | Execute attack chains without recompiling or restart ARTC2. Currently supports three different attack functions. Attack Chains, Attack Profiles, and Attack Scenarios|
| Modular Payload Delivery | ARTC2 le SILENTRINITY's framework uses unmanaged powershell and stageless powershell stagers to compile and execute Red Team Atomic test payloads in memory, *"AS IS"*
| Operational Management | Job IDs are included for controller execution and e collection. They're great for event analysis and e correlation. "job_id": "D3l820IWpyi67"| Atomic Updates | The ART port pipeline is triggered by repo updates at ATOMIC-RED-TEAM
</br>
</br>
Organizations need to:
</br>
By default, ARTIC-C2 logs are written to ARTIC-C2's current working directory in ./logs/.
Session logs include:
</br>
utc_timestamp: UTC timestampsession: Target session GUIDjob_id: Unique Job execution IDttp_data: Technique IDe: Base64 encoded e collected from a breach point targete: Status to indicate if the TTP executed was blocked. </br>
</br>
EXECUTION SIGNATURE HEADER
Execution signature headers are used to if any defenses block atomics. Sometimes, the atomic commands may not return data in STDOUT. However, if the execution signature header returns header information, then this indicates the source code compiled, loaded into the CLR, and executed on the target breach point. The execution signature header includes:
PID: used during technique executionDate: UTC stamp produced from the breach point targetIsHighIntegrity: Process integrity statusHostName: breach point target hostnameCurrentUser: Current user. Great for tracking when users are impersonatedIsUserAdmin: Admin statusIPv4: IPv4 address infoIPv6: IPv6 address info</br>
</br>
SAMPLE EXECUTION EVENT LOG
T1069.001-2 was executed in memory
</br>
</br>
SAMPLE E COLLECTION LOG
E was collected from the target breach point after executing T1069.001-2.
<br/>
<br/>
SAMPLE HEADER SIGNATURE
</br>
</br>
SAMPLE BASE64 DECODED E LOG
#### Listeners
By default, listeners bind to the system's interface with HTTPS:443 and HTTP:80. They must be accessible from the assumed breach point target. Set your Callback URLs in the :> listeners context before generating any stager.
</br>
</br>
1. git clone
2. cd ./Atomic-Red-Team-intel-C2
3. ./install.sh install
</br>
</br>
DEPLOYMENT OPTIONS
ARTIC-C2 enables flexible deployment models to suit all atomic test case execution requirements. While there are a few client-side console dependencies relative to caching, the client console is not required to run on the same system as the team server. Soon, we'll package and release a dedicated client.
NOTE: The examples below assume ARTIC-C2 will start from the same instance.
Start WSS on the default port and produce an ad-hoc log
artic2.py wss 127.0.0.1 Art1.c25rvr >> /var/log/artic2.log &artic2.py client wss://operator:Art1.c25rvr@127.0.0.1:5000</br>
</br>
Start WSS on the default port in the foreground
artic2.py wss 127.0.0.1 Art1.c25rvrartic2.py client wss://operator:Art1.c25rvr@127.0.0.1:5000</br>
</br>
Start WSS on port 5443, bind to 10.0.0.43, produce adhoc log and connect two clients
artic2.py wss 10.0.0.43:5443 Art1.c25rvr >> /var/log/artic2.log &artic2.py client wss://operator1:Art1.c25rvr@10.0.0.43:5443artic2.py client wss://operator2:Art1.c25rvr@10.0.0.43:5443</br>
</br>
</br>
</br>
开发语言:Python
Star 数:178
该项目属于红蓝攻防方向的开源资源,代码结构清晰,适合安全研究人员学习参考。项目围绕ARTi-C2 is a post-exploitation framework used to execute Atomic Red Team test cases with rapid payload deployment and execution capabilities via .NET's DLR.展开,提供了可运行的实现,对理解相关安全机制、工具原理与攻防技术具有较高的研究价值。
从技术实现角度看,此类项目的核心在于对底层原理的深入理解与工程化落地。开发者在研究过程中可以结合官方文档与社区讨论,梳理项目的初始化流程、核心模块职责与数据流转,逐步掌握其中的技术细节与设计思路。
1. 下载源码压缩包,解压到本地环境。
2. 根据项目类型准备对应的运行环境与依赖。
3. 按照 README 中的步骤完成配置与部署。
4. 在隔离的测试环境中运行验证,避免影响生产系统。
本资源来源于开源社区,仅供安全研究、技术学习与合法授权范围内的攻防演练使用,请勿用于任何非法或侵害他人权益的用途。使用本项目产生的一切后果由使用者自行承担。
| 资源标题 | Atomic-Red-Team-C2 - ARTi-C2 is a post-exploitation framework used to |
| 所属分类 | 红蓝攻防 |
| 发布作者 | admin |
| 发布时间 | 2026-10-06 00:47:53 |
| 下载权限 | 免费下载 |
| 附件数量 | 2 个下载链接 |
| 浏览次数 | 409 |
| 讨论数量 | 0 |
| 主题状态 | 正常讨论中 |