Analysis updated 2026-08-04 · repo last pushed 2025-05-19
Modify a Cobalt Strike beacon profile so it evades antivirus during an authorized security assessment.
Analyze a legitimate Windows DLL file to generate configuration that helps injected code blend in.
Generate safe file header values that keep beacon code functional without triggering security alarms.
Use one of three ready-made profile templates directly on a Cobalt Strike server.
| ridter/malleable-cs-profiles | 0xallam/posthog | 0xallam/search-engine | |
|---|---|---|---|
| Stars | 1 | 1 | 1 |
| Language | — | Python | C++ |
| Last pushed | 2025-05-19 | 2026-03-26 | 2023-08-23 |
| Maintenance | Stale | Maintained | Dormant |
| Setup difficulty | hard | moderate | hard |
| Complexity | 4/5 | 3/5 | 3/5 |
| Audience | ops devops | pm founder | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires a working Cobalt Strike environment, a Windows DLL to analyze, and existing knowledge of how Cobalt Strike beacons operate, this is not a standalone tool.
This is a collection of Python tools for red team operators and security researchers who use Cobalt Strike, a popular penetration testing tool. The project helps users create "OPSEC-safe" configuration profiles that make Cobalt Strike's beacons (the agent that runs on a target machine) harder for security software like EDR (Endpoint Detection and Response) systems to detect. At a high level, the tools work by modifying the code that Cobalt Strike injects into a target system to make it look less suspicious. One script adds junk instructions at the beginning of the code to throw off pattern-matching detection. Another script analyzes a legitimate Windows DLL file and generates configuration so the malicious code blends in and looks like a normal system component. A third script generates safe values for file headers that need to remain readable for the code to function but can still trigger security alarms if not handled carefully. The target audience is professional penetration testers and red teamers who conduct authorized security assessments. For example, if a red team is simulating an attack and their Cobalt Strike beacon keeps getting caught by a company's antivirus, they would use these tools to modify the beacon's profile so it slips past defenses undetected. The project also includes three ready-to-use profile templates that users can plug directly into their Cobalt Strike server. It is worth noting that two of the scripts in the project are marked as deprecated, meaning they no longer work as intended or have become obsolete. The project also ties into a detailed blog post series that explains the underlying concepts. These tools sit firmly in the offensive security space and assume the user already has a working understanding of how Cobalt Strike operates.
A collection of Python scripts that help penetration testers create harder-to-detect configuration profiles for Cobalt Strike, a popular authorized security testing tool, by modifying code to evade antivirus and EDR detection.
Stale — no commits in 1-2 years (last push 2025-05-19).
No license information is provided, so default copyright restrictions apply and you should contact the author before using this code.
Setup difficulty is rated hard, with roughly 1h+ to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Verify against the repo before relying on details.