π€1
π₯1
COPYRIGHT DOES NOT EXIST
Linus Walleij, 1998
p.s: There interesting story about hacker and computer
https://www.devili.iki.fi/pub/misc/books/cdne.pdf
Linus Walleij, 1998
p.s: There interesting story about hacker and computer
https://www.devili.iki.fi/pub/misc/books/cdne.pdf
Dissecting-the-Arsenal-of-LockBit-HuiSeong-Yang.pdf
14.4 MB
Dissecting the Arsenal of LockBit
Hui Seong-Yang
π«£ staring to one of you who want start RAAS *pun intended
Hui Seong-Yang
π«£ staring to one of you who want start RAAS *pun intended
Bruce_Dang,_Alexandre_Gazet,_Elias_Bachaalany,_SΓ©bastien_Josse_Practical.pdf
4.6 MB
Practical Reverse Engineering: x86, x64, ARM, Windows Kernel, reversing tools, and obfuscation (2014)
Bruce Dang, Alexandre Gazet, Elias Bachaalany, SΓ©bastien Josse
This truly practical book from page 2 you already throw by reading assembly, despite kind of masochistic nature, it scale well which make it fun to read *ehem* with good amout of free time. If you want to understand the point of reversing, I suggest read this first: https://t.me/compsciresources/245
Bruce Dang, Alexandre Gazet, Elias Bachaalany, SΓ©bastien Josse
This truly practical book from page 2 you already throw by reading assembly, despite kind of masochistic nature, it scale well which make it fun to read *ehem* with good amout of free time. If you want to understand the point of reversing, I suggest read this first: https://t.me/compsciresources/245
β€βπ₯1
Producing Open Source Software
How to Run a Successful Free Software Project
https://producingoss.com/en/producingoss-b5.pdf
How to Run a Successful Free Software Project
https://producingoss.com/en/producingoss-b5.pdf
Rui_Ueyama_Introduction_to_creating_a_C_compiler_for_those_who_want.pdf
1 MB
Introduction to creating a C compiler for those who want to know the lower layer
Rui Ueyama
note: the image can't translated
Rui Ueyama
note: the image can't translated
β€βπ₯4
Forwarded from vx-underground
One thing noobie scoobies don't seem to understand is that malware is literally just software. Understandably, that seems kind of obvious, it's in the name β 'malicious software'. But it seems less obvious to some that, in order to write malware, you apply the exact same principles, techniques, and structures that legitimate software uses.
Malware is regular ol' programming with some sprinkles of weird stuff. These weird things are documented and shared. Some try to find new weird things.
When people ask what language is best for malware... it's kind of like asking 'what's the best ice cream flavor?'. It's entirely subjective. Everyone will tell you something different. You'll notice a lot of people will prefer Chocolate or Vanilla, you may encounter some who like Raspberry Banana Sprinkle Jam-Blam Blast, or Minty Schminty SpongeBob Sticks Bombs, but at the end of the day it's all still ice cream.
In it's most simple form, all malware techniques are things legitimate software may do.
Ransomware?
- Step 1. Enumerate files in a directory
- Step 2. Lock and encrypt files
Information Stealers?
- Step 1. Enumerate files in a directory
- Step 2. Upload files somewhere
RATs?
- Step 1. Make program run at start
- Step 2. Execute commands (cmd, powershell, other programs)
- Step 3. Upload files somewhere
Loaders?
- Step 1. Download file from somewhere
- Step 2. Run file
Everything the malware does is just an expansion of what is explained above.
Want to find new malware techniques? Find new ways to execute a process, find new ways to enumerate files in a directory, file new ways to upload files somewhere, find new ways to download files from somewhere, find new ways to write to files or delete files, etc.
How do you do this? Read. Read everything. Blogs, Windows documentation, StackOverflow, Wikipedia, our website. Look at every DLL you find on your computer in Ida or Ghidra, just open stuff and look around. Look at other peoples work and see if you can expand on it and find something new.
tl;dr learn to code, then learn weird stuff
Malware is regular ol' programming with some sprinkles of weird stuff. These weird things are documented and shared. Some try to find new weird things.
When people ask what language is best for malware... it's kind of like asking 'what's the best ice cream flavor?'. It's entirely subjective. Everyone will tell you something different. You'll notice a lot of people will prefer Chocolate or Vanilla, you may encounter some who like Raspberry Banana Sprinkle Jam-Blam Blast, or Minty Schminty SpongeBob Sticks Bombs, but at the end of the day it's all still ice cream.
In it's most simple form, all malware techniques are things legitimate software may do.
Ransomware?
- Step 1. Enumerate files in a directory
- Step 2. Lock and encrypt files
Information Stealers?
- Step 1. Enumerate files in a directory
- Step 2. Upload files somewhere
RATs?
- Step 1. Make program run at start
- Step 2. Execute commands (cmd, powershell, other programs)
- Step 3. Upload files somewhere
Loaders?
- Step 1. Download file from somewhere
- Step 2. Run file
Everything the malware does is just an expansion of what is explained above.
Want to find new malware techniques? Find new ways to execute a process, find new ways to enumerate files in a directory, file new ways to upload files somewhere, find new ways to download files from somewhere, find new ways to write to files or delete files, etc.
How do you do this? Read. Read everything. Blogs, Windows documentation, StackOverflow, Wikipedia, our website. Look at every DLL you find on your computer in Ida or Ghidra, just open stuff and look around. Look at other peoples work and see if you can expand on it and find something new.
tl;dr learn to code, then learn weird stuff
π5
networking_manual_by_bassterlord.pdf
5.6 MB
Networking Manual
Bassterlord
p.s: APT-ing guide
Bassterlord
p.s: APT-ing guide
2405.04109v1.pdf
5.9 MB
The Malware as a Service ecosystem
Constantinos Patsakis, David Arroyo, and Fran Casino
Constantinos Patsakis, David Arroyo, and Fran Casino
π₯2
https://attl4s.github.io/assets/pdf/Understanding_a_Payloads_Life.pdf
Daniel LΓ³pez JimΓ©nez
Daniel LΓ³pez JimΓ©nez