explaingit

bypass007/emergency-response-notes

5,548Audience · ops devopsComplexity · 3/5Setup · easy

TLDR

A Chinese-language security reference covering computer intrusion response for Windows and Linux: detecting webshells, analyzing logs, identifying attacker persistence techniques, and walking through real ransomware and cryptomining case studies.

Mindmap

mindmap
  root((emergency-response-notes))
    What it does
      Intrusion response guide
      Case-based reference
      Chinese language
    Topics
      Webshell detection
      Log analysis
      Persistence techniques
    Platforms
      Windows incidents
      Linux incidents
    Case Studies
      Ransomware
      Cryptomining malware
      DDoS and rootkits
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Follow structured incident response steps for a compromised Windows or Linux server, from initial detection through cleanup and hardening.

USE CASE 2

Learn how to analyze Windows event logs, Linux system logs, and web server access logs to trace an attacker's activity timeline.

USE CASE 3

Study real case studies of ransomware, cryptomining malware, DDoS infections, and rootkits to recognize the same patterns in your own environment.

Getting it running

Difficulty · easy Time to first run · 5min

Documentation-only reference, no installation required, read online via the linked GitBook site.

No license is specified for this documentation project.

In plain English

Emergency Response Notes is a Chinese-language reference collection for security engineers who need to investigate and handle computer intrusion incidents. The author describes it as personal study notes built up from real case analysis, covering the full arc from discovering that a system was compromised through to cleaning it up. The content is organized into six chapters. The first covers intrusion investigation on both Windows and Linux systems, including how to detect webshells (files attackers plant on web servers to maintain access) and how to respond to ransomware infections. The second chapter is about log analysis, covering Windows event logs, Linux system logs, web server logs, and database logs from MySQL and MSSQL. The third chapter addresses persistence techniques, meaning the methods attackers use to keep access even after a victim reboots or patches. It covers hidden files and backdoors on both Windows and Linux, file download methods, and common webshell management tools used by attackers. The fourth and fifth chapters walk through practical Windows and Linux case studies, including FTP brute-force attacks, trojan viruses, ransomware, cryptomining malware, DDoS infections, and rootkits. The sixth chapter focuses on web-specific incidents: sites that had webshells injected, sites hijacked to serve cryptomining scripts, bulk defacement attacks, hijacking of news sources and mobile traffic, search engine hijacking, and administrator account tampering. The project is defensive in nature. The intended reader is a security professional or aspiring security engineer who wants case-based guidance on what to look for and how to contain damage after a breach. The README is in Chinese, and the full content is published as a GitBook site.

Copy-paste prompts

Prompt 1
Using emergency-response-notes as a guide, list the first five things I should check on a compromised Linux web server to determine whether a webshell was planted and how to find it.
Prompt 2
I suspect my Windows server was hit with ransomware. Based on emergency-response-notes, walk me through the log analysis steps to find when the attacker first gained access.
Prompt 3
Following emergency-response-notes, what persistence mechanisms should I look for on a Linux server after a suspected intrusion, and what shell commands detect each one?
Prompt 4
I found unusual processes on a server. Using the emergency-response-notes methodology, explain how to distinguish a cryptomining infection from a rootkit and the cleanup steps for each case.
Open on GitHub → Explain another repo

← bypass007 on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.