Skip to content

Update link to blogpost in README #79

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
felixm-pw merged 2 commits into from
Jan 20, 2023
Merged

Update link to blogpost in README #79

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
62d027e
Update link to blogpost in README
rgmz Jan 9, 2023
67bd468
docs: fix broken images in guides
rgmz Jan 16, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ C3 (Custom Command and Control) is a tool that allows Red Teams to rapidly devel

## Usage

See [this](https://labs.mwrinfosecurity.com/tools/c3) blog post for a detailed tutorial.
See [this](https://labs.withsecure.com/tools/c3) blog post for a detailed tutorial.

For contribution guide (how to develop a Channel tutorials), see [this page](CONTRIBUTING.md).

Expand Down
4 changes: 2 additions & 2 deletions Res/C2ImplementationGuide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ Finally, for ease of integration it helps if the chosen framework provides acces

At a high level, the objective of integration would result in the communication flow described in the figure below:

<img src="images\C2ImplementationGuide\01.png"/>
![](./Images/C2ImplementationGuide/01.png)



Expand Down Expand Up @@ -137,7 +137,7 @@ FSecure::ByteView FSecure::C3::Interfaces::Connectors::Covenant::GetCapability()
```
The resulting form is shown in the next figure. Note that no changes were made to the actual web interface of C3.

<img src="images/AttachingCovenantGrunt/figure1.png" />
![](./Images/AttachingCovenantGrunt/figure1.png)

**Stage 2 - Handle User Input**

Expand Down
4 changes: 2 additions & 2 deletions Res/RelayGuides/AttachingCovenantGrunt.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,13 +4,13 @@ This section demonstrates how to use the new integration of the Covenant C2 fram

2. Fill in the form, these options will be used to create a BridgeListener in Covenant on the specified port.

<img src="../images/AttachingCovenantGrunt/figure1.png"/>
![](../Images/AttachingCovenantGrunt/figure1.png)

3. Run the C2Bridge project on the same system as C3’s gateway. If TCP port 8000 was chosen as the C2Bridge port, then the correct arguments for C2Bridge would be “dotnet C2Bridge.dll covenant-host-ip 8000 8000”.

4. In order to stage an SMB Grunt, select a running Node Relay’s command centre and select AddPeripheralGrunt.

<img src="../images/AttachingCovenantGrunt/figure2.png"/>
![](../Images/AttachingCovenantGrunt/figure2.png)



2 changes: 1 addition & 1 deletion Res/ShellcodeUsageGuide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ It is now possible for raw shellcode to be downloaded from the web interface. Th

3. Within the Relay Setup window, select “shellcode” from the target suffix dropdown. A new set of options will be provided, as shown in the next image.

<img src="images/ShellcodeUsageGuide/figure3.png"/>
![figure3.png](./Images/ShellcodeUsageGuide/figure3.png)

1. Select the various options that will be passed to Donut. Note that it is strongly advised to use compression, of which the apLib option is the best.

Expand Down