Skip to content

johnax0/OCMar

Repository files navigation

OCMaR

Open for Collab Malware Research

Included malware(s) database are only for educational purposes!

Feature:

  1. Malware Type
  2. Sample
  3. Indication of Suspicious Actions
  4. Payload/Dangerous Functions
  5. Ways to immobilize

Explaination regarding releases:

  • Malware(s) will be filled accordingly to the collaboration of the people that helps with reversing malware that are already available or that is coming.
  • False-Positive(s) will be filled to show that the software is not actually dangerous and does not have any dangerous functions within it.

Guidance on what you need and how-to (Briefly)

For Details, here is the explained guidance with pictures. Feel free to check them!

========================================================================================================================================================================================

->For those who are new, we will start with Sandbox or VMWare. Sandbox/VMWare needed to be used to prevent the malware from activating and running on the host (your main computer), therefore the activity and the length of what malware can do is or at least limited.<-

Full Guide

  1. To install VMWare, you can go here https://www.vmware.com/products/workstation-pro/workstation-pro-evaluation.html and download the file needed. Afterwards, follow the steps needed.

  1. Prepare to install windows ISO File from here https://support.microsoft.com/id-id/windows/create-an-iso-file-for-windows-10-38547366-1dcb-7afd-1726-9eb222d72705.

  1. The windows ISO File can be downloaded by downloading a Media Creation Tool and Follow the steps to install it on USB/as a ISO File.

  1. Create a new device in VMWare that you just downloaded. Select the ISO File and configure the system, then complete the windows setup.

  1. Download Necessary Tools to analyze the malware such as: For Static Analysis: ExeinfoPE, PEStudio, APK Editor / apktool

    For Dynamic Analysis: Procmon, Procdot, Fakenet-ng For Reverse and Patching: Ghidra Disassembler, X64dbg / X32dbg
  2. Ghidra Disassembler requires you to have Java 17 64-bit Runtime and Development Kit (JDK), there are few sources to install from:

  3. Procdot, you will need WinDump/TCPDump and Graphviz to be able to create a visualization of the processes. You can download from here:

  4. Step by step Instructions on How to Analyze (Windows Malware)

  • Open up VMWare, and disconnect/the internet just to be cautios of the malware. While you do so, the windows defender should be turned off to prevent any interference from it.

  • Static Analysis, drag and drop the executables that you want to analyze inside of Exeinfope and PEStudio to analyze it further. Exeinfope will give you an information if the malware is packed and the good part is, it also tells you how to unpack. PEStudio will tell you indications on what functions/api that will be used alongside the windows libraries file.

  • Dynamic Analysis, before trying to run the malware it is recommended to start fakenet-ng incase the malware is trying to connect to an external network/IP. Procmon can be used to capture and log the activity of the malware. Filter can be applied also into the captured logs, those filter are ProcessCreate, WriteFile, SetDispositionInformationFile, TCP and UDP, & RegSetValue

ProcessCreate can show the malware is creating a new process when it is executed, while WriteFile and SetDispositionInformationFile is tracking what file or temporary files are created. RegSetValue also keep tracks of the value of registry that are being set. TCP and UDP are to logs if the malware is requesting a request to external IP/Websites. Afterwards, Procmon can create/export the logs using CSV so that Procdot can read them.

While using Procdot, you can use the CSV file that you got from Procmon and insert them. Pick the process of the malware that was running on the device and hit refresh to visualize the process.

  • Disassembly and Patching: Ghidra, you can use it to analyze the executables. It will analyze the imports such as functions and necessary DLL file that are being used also being able to decompile some part of the malware is a nice thing to have.

  • By doing decompile on the code, you can analyze what conditions does it have to run certain functions and/or finds out what is the killswitch. Finally, after you have got the killswitch and analyze the conditions you can import/open the executeables in X64dbg or X32dbg to patch that specific functions. You can either change the value like changing from 1 to a 0 or going with the NOP on functions that are marked as suspicious/dangerous.

And that's all about it. Feel free to let me know if you have any different ways so I can add it into this guide/make a alternative guidance. Thanks !

About

Open for Collab Malware Research

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published