https://github.com/cado-security/rip_raw

Rip Raw is a small tool to analyse the memory of compromised Linux systems.
https://github.com/cado-security/rip_raw

dfir dfir-automation forensic-analysis forensics memory-forensics security

Last synced: about 1 month ago
JSON representation

Rip Raw is a small tool to analyse the memory of compromised Linux systems.

• Host: GitHub
• URL: https://github.com/cado-security/rip_raw
• Owner: cado-security
• License: apache-2.0
• Created: 2022-01-27T17:36:10.000Z (over 2 years ago)
• Default Branch: main
• Last Pushed: 2022-01-31T21:25:40.000Z (over 2 years ago)
• Last Synced: 2024-06-06T20:03:33.338Z (3 months ago)
• Topics: dfir, dfir-automation, forensic-analysis, forensics, memory-forensics, security
• Language: Python
• Homepage:
• Size: 914 KB
• Stars: 132
• Watchers: 8
• Forks: 16
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

• awesome-hacking-lists - cado-security/rip_raw - Rip Raw is a small tool to analyse the memory of compromised Linux systems. (Python)

README

        

# Rip Raw #

Rip Raw is a small tool to analyse the memory of compromised Linux systems.

It is similar in purpose to Bulk Extractor, but particularly focused on extracting system Logs from memory dumps from Linux systems. This enables you to analyse systems without needing to generate a profile.

This is not a replacement for tools such as Rekall and Volatility which use a profile to perform a more structured analysis of memory.

Rip Raw works by taking a Raw Binary such as a Memory Dump and carves files and logs using:

* Text/binary boundaries

* File headers and file magic

* Log entries

Then puts them in a zip file for secondary processing by other tools such as Cado Response or a SIEM such as Splunk (examples below).

### Example ###

For example, after capturing the memory of an Amazon EKS ( Elastic Kubernetes Service) system compromised with a crypto-mining worm we processed it with rip_raw:

    python3 rip_raw.py -f eks-node-ncat-capture.mem

 

And then the large zip of logs that Rip Raw outputs can be viewed in a tool such as Cado Response (below). Approximately **36500 log events** were extracted from this memory image, along with a number of binaries such as images and executables.

![Screenshot](screenshots/1.png "Screenshot")

Or Splunk:

![Screenshot](screenshots/2.png "Screenshot")

### Learn More ###

* We'll be giving a webinar on Cloud Incident Response and Ransomware on Tuesday February 1st @ 

* We give an example of Rip Raw for analysing a compromised Amazon Kubernetes system in a talk @ 

* You can download a PDF copy of our playbook on how to respond to compromised Kubernetes systems such as Amazon EKS @