explaingit

mantvydasb/redteaming-tactics-and-techniques

4,590PowerShellAudience · developerComplexity · 4/5Setup · hard

TLDR

A personal research notebook of offensive security techniques for penetration testers, covering code execution, process injection, lateral movement, persistence, and detection evasion in authorized lab environments.

Mindmap

mindmap
  root((ired.team notes))
    What it is
      Personal research notes
      Published as ired.team
    Topics
      Code execution
      Process injection
      Lateral movement
      Persistence
      Evasion techniques
    Audience
      Pentesters
      OSCP students
      Security researchers
    Platform
      Windows internals
      PowerShell
      System APIs
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

Study Windows penetration testing techniques with working code examples for OSCP exam preparation in a lab environment.

USE CASE 2

Research how specific attack methods like process injection work and what forensic traces they leave for defenders to find.

USE CASE 3

Build a reference library of offensive techniques to use during authorized penetration testing engagements.

Tech stack

PowerShellC#Windows

Getting it running

Difficulty · hard Time to first run · 1day+

Requires a dedicated lab environment with Windows VMs and security tools to safely test techniques, assumes prior familiarity with Windows internals and command-line tools.

In plain English

This repository is a personal notebook of offensive security research, maintained by a security professional who goes by the handle spotheplanet. The notes document experiments with the kinds of techniques that penetration testers and red teamers use when assessing the security of computer systems in controlled, authorized lab environments. The same content is published as a website at ired.team. Red teaming is a practice where a group of security specialists tries to break into an organization's systems using the same methods a real attacker might use, so that defenders can find and fix weaknesses before a genuine threat actor does. The notes here cover areas like getting code to run on a target machine, injecting code into running processes, moving across a network, staying persistent after an initial foothold, and avoiding detection by security tools. The author is clear about the purpose: this is a learning resource built by doing hands-on experiments and documenting the results. Most of the techniques covered were discovered by other researchers in the security community, and the author tries to credit original sources throughout. The notes are not meant to be exhaustive or perfectly accurate, and the README itself warns readers to verify claims against other sources rather than treating anything here as definitive. The repository is aimed at people already working in security or studying for certifications like OSCP, a well-known hands-on penetration testing qualification. The content assumes familiarity with Windows internals, command-line tools, and concepts like process memory and system APIs. It is not an introduction to security for beginners, but rather a reference library of techniques with code examples and explanations of how each method works and what traces it leaves behind.

Copy-paste prompts

Prompt 1
Based on common red team techniques, show me a PowerShell example for injecting shellcode into a remote process and explain which Windows API calls are involved at each step.
Prompt 2
What are the most common persistence mechanisms a penetration tester would check and test during a Windows red team engagement, and how does each one survive a reboot?
Prompt 3
I'm studying for my OSCP. Help me create a structured study plan covering key lateral movement techniques like pass-the-hash and WMI execution, starting with the fundamentals.
Prompt 4
Show me how to use common Windows living-off-the-land binaries to execute code during a penetration test without dropping additional executables to disk.
Open on GitHub → Explain another repo

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

Verify against the repo before relying on details.