Open
Conversation
Collaborator
Author
🔗 Additional ContextOriginal Blog Post: https://github.com/EricEsquivel/CobaltStrike-Linux-Beacon Content Categories: Based on the analysis, this content was categorized under "Windows Hardening -> Cobalt Strike (add subsection for custom implants / non-Windows beacons) or Generic Hacking -> Exfiltration / Tunneling and Port Forwarding (SOCKS pivoting via implant) with cross-reference from Cobalt Strike". Repository Maintenance:
Review Notes:
Bot Version: HackTricks News Bot v1.0 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 Automated Content Update
This PR was automatically generated by the HackTricks News Bot based on a technical blog post.
📝 Source Information
🎯 Content Summary
What this is
This GitHub repository is a Proof-of-Concept (PoC) offensive implant: a custom Cobalt Strike “Beacon-like” agent for Linux written in C that can be controlled from a Cobalt Strike Team Server by correctly implementing the Cobalt Strike HTTP/S protocol (using the default C2 profile). It is not a CVE write-up or a product vulnerability; the “security impact” is that it provides an attacker-controlled implant that enables command exe...
🔧 Technical Details
Custom-implant technique: Implement the Cobalt Strike Team Server’s expected HTTP/S communication (here, the default C2 profile) to build a fully custom “Beacon-like” agent for any platform while retaining Cobalt Strike’s operator workflow. Once the protocol is matched, the operator can task the implant (sleep/cd/pwd/shell/ls/exit/upload/download) and receive responses via standard listener traffic.
Linux post-exploitation extensibility: Add modular capability by executing Linux Beacon Object Files (BOFs) within the implant process using an ELF loader (e.g., TrustedSec’s ELFLoader). This allows operators to run BOF-based functionality (including TrustedSec and Outflank-style BOFs) in-memory/in-process, effectively extending the implant beyond its built-in commands without rewriting the core agent.
Pivoting via implant: Embed a SOCKS proxy inside the beacon to tunnel/proxy operator traffic through the compromised host, enabling access to internal services and networks ...
🤖 Agent Actions
Updated windows-hardening/cobalt-strike.md with a new subsection on building custom/non-Windows Cobalt Strike implants (Linux beacon PoC): covering protocol compatibility with default HTTP/S profiles, Aggressor Script payload generation, implemented task handlers, Linux BOF execution via ELFLoader/Outflank templates, and embedded SOCKS pivoting behavior. Added a comprehensive References section citing the PoC repo and related protocol/BOF resources.
This PR was automatically created by the HackTricks Feed Bot. Please review the changes carefully before merging.