Skip to content

Commit 2544706

Browse files
Update README.md
1 parent 7a3ee1a commit 2544706

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

README.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,10 +5,11 @@ This repository was created in conjunction with a Packer Development Workshop he
55

66
<br>
77
<div align="center">
8-
<img src="https://github.com/rtecCyberSec/Packer-Development/assets/27858067/1ce772fd-92b2-4dea-8c0c-30d77a2b76a2" width="500">
8+
<img src="https://github.com/rtecCyberSec/Packer_Development/assets/27858067/756b23d5-8c13-4011-ab43-02147d2c12e8" width="500">
99
</div>
1010
<br>
1111

12+
1213
The goal of the workshop is to show participants the concept of packed malware. How does a Packer work technically? Using public toolings without modifications from Github (including this repo's examples ;-)) will nowadays lead to Red Teams or Threat Actors getting caught real quick. To avoid detections, it's therefore needed to build custom tooling and/or to learn about Malware Development in general. Automating the process of taking an input payload, encrypting it, building loader code and compiling that afterward saves a lot of time for operators.
1314

1415
How does a Packer work technically? How to load/execute C# assemblies, PE's or Shellcode from memory on runtime? How to get rid of entropy based detections? Which evasion techniques should be integrated? How about Sandbox evasion and Anti-Debugging techniques or environmental keying? Answers to these questions are included within this repository.

0 commit comments

Comments
 (0)