whatisgithub

What is malleable-cs-profiles?

ridter/malleable-cs-profiles — explained in plain English

Analysis updated 2026-08-04 · repo last pushed 2025-05-19

1Audience · ops devopsComplexity · 4/5StaleSetup · hard

In one sentence

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.

Mindmap

mindmap
  root((repo))
    What it does
      Creates OPAC profiles
      Modifies beacon code
      Generates safe values
    Tech stack
      Python scripts
      Cobalt Strike
      Windows DLLs
    Use cases
      Evade EDR detection
      Slip past antivirus
      Authorized attack sims
    Audience
      Red team operators
      Penetration testers
      Security researchers
    Notes
      Two scripts deprecated
      Includes profile templates
      Ties to blog series

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Modify a Cobalt Strike beacon profile so it evades antivirus during an authorized security assessment.

USE CASE 2

Analyze a legitimate Windows DLL file to generate configuration that helps injected code blend in.

USE CASE 3

Generate safe file header values that keep beacon code functional without triggering security alarms.

USE CASE 4

Use one of three ready-made profile templates directly on a Cobalt Strike server.

What is it built with?

PythonCobalt Strike

How does it compare?

ridter/malleable-cs-profiles0xallam/posthog0xallam/search-engine
Stars111
LanguagePythonC++
Last pushed2025-05-192026-03-262023-08-23
MaintenanceStaleMaintainedDormant
Setup difficultyhardmoderatehard
Complexity4/53/53/5
Audienceops devopspm founderdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · hard Time to first run · 1h+

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.

No license information is provided, so default copyright restrictions apply and you should contact the author before using this code.

So what is it?

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.

Copy-paste prompts

Prompt 1
I have a Cobalt Strike beacon that keeps getting caught by EDR during an authorized assessment. Using the malleable-cs-profiles Python tools, help me modify the beacon's profile to add junk instructions at the beginning of the code to throw off pattern-matching detection.
Prompt 2
Help me use the script from ridter/malleable-cs-profiles that analyzes a legitimate Windows DLL file and generates a Cobalt Strike configuration profile so my beacon code blends in and looks like a normal system component.
Prompt 3
Walk me through using the malleable-cs-profiles tool to generate safe values for file headers in my Cobalt Strike beacon so the code stays functional but does not trigger security alarms.
Prompt 4
I want to use one of the ready-to-use profile templates from the malleable-cs-profiles repo on my Cobalt Strike server. Help me pick the right template and explain how to plug it in.
Prompt 5
Two scripts in the malleable-cs-profiles repo are marked deprecated. Help me understand which scripts still work and how to use the active ones to create an OPSEC-safe Cobalt Strike profile.

Frequently asked questions

What is malleable-cs-profiles?

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.

Is malleable-cs-profiles actively maintained?

Stale — no commits in 1-2 years (last push 2025-05-19).

What license does malleable-cs-profiles use?

No license information is provided, so default copyright restrictions apply and you should contact the author before using this code.

How hard is malleable-cs-profiles to set up?

Setup difficulty is rated hard, with roughly 1h+ to a first successful run.

Who is malleable-cs-profiles for?

Mainly ops devops.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.