intel-codex - Open-source field manual for OSINT, DFIR and cyber

项目说明

---
title: "Intel Codex"
description: "Operational manual for digital in: OSINT platform techniques, security procedures, forensics and real-world case studies."
---

Intel Codex

![Intel Codex]()

The open-source field manual for OSINT, DFIR and cybersecurity in.

Standard operating procedures for in, security researchers and CTF players.
Written to be executed during a case, not read once and bookmarked.

OSINT · DFIR · Malware · Pentesting · Blockchain · Cloud · OPSEC · CTF

![Vault check]()
![Browse online]()
![Obsidian]()
![License]()
![Contributions]()

<!-- :begin (generated by tools/build-.sh — do not edit by hand) -->
41 SOPs · 20 in · 21 security
<!-- :end -->

This is not a link list and not a tool dump. Each SOP is a full procedure: scope and
legal boundaries, the commands to run on Windows, Linux and macOS, what the output
means, how to preserve it as e, and where to hand off. The malware SOP is 2,385
lines; the web application one is 3,588.

Claims that were checked against a primary source carry a dated marker in the text.
Status publishes that record per SOP: how many
checks it carries, when the oldest was made, and how old that makes it. Nothing here
is labelled field-tested, because nothing here has the e for it.

---

Three ways to use it

| | |
|---|---|
| Read it online | lecodex.xyz — full-text search, graph view, no install |
| Run it locally | Clone this repo and open it as an Obsidian vault: backlinks, graph, offline |
| Improve it | Fork, edit the Markdown, open a PR. See CONTRIBUTING.md |

---

A sense of the depth

---

Where to look

| In | Analyze | Assess | Practice |
|---|---|---|---|
| OSINT techniques | Malware | Pentesting | CTF |
| Social platforms | Forensics | Web & mobile | Writeups |
| Dark web | Cloud forensics | Acti | Case studies |
| Financial & AML | Email & BEC | Cloud & containers | Exercises |

Full listings: In · Security · CTF

---

Start here

Whatever you are in, these two come first:

1. Legal & Ethics Review — authorization and compliance before collection
2. OPSEC Planning — attribution separation, infrastructure hygiene

Then pick your track:

| You are | Go to |
|---|---|
| An in | Platform SOPs, then Collection Log and Entity Dossier |
| A security analyst | Malware Analysis and Hash Generation |
| A pentester | Pentesting Index, scoped to your engagement |
| A CTF player | Challenge Methodology and Cheat Sheets |
| Learning from zero | In Workflow, then the example case |

---

Quick start

Requires Obsidian v1.0+. Or skip the install and read it on lecodex.xyz.

---

Learning paths

Six 6-week tracks. Each links the SOPs in order.

| Track | Weeks 1–2 | Weeks 3–4 | Weeks 5–6 |
|---|---|---|---|
| In | Legal + OPSEC + platforms | Image/Video, Financial | Practice + reporting |
| Security analyst | Malware fundamentals | Reverse engineering | Ad malware, IOC generation |
| Pentester | Web app security | Linux + AD | Mobile + firmware |
| Bug bounty | Web app + bug bounty | research | Li |
| CTF | Reverse engineering + crypto | Pwn and web challenges | Competition practice |
| DFIR | Forensics + hashing | Malware + incident response | Memory forensics, timelines |

---

What makes it different

---

Contributing

Contributions are welcome, from a typo to a whole new SOP. Fork, branch, edit, update the relevant index, open a PR. Con, style guide and review process are in CONTRIBUTING.md.

---

Legal & ethics

This vault is for educational and authorized in purposes only.

Users are responsible for compliance with applicable law.

---

More from gl0bal01

OSINT Foundations · Cybersecurity · Reverse Engineering · AI · Cheatsheets

License

MIT. If you use or fork this vault, attribution is appreciated.

*Built with Obsidian.*

项目信息

开发语言：Shell

Star 数：62

技术要点

该项目属于CTF思路方向的开源资源，代码结构清晰，适合安全研究人员学习参考。项目围绕Open-source field manual for OSINT, DFIR and cybersecurity investigations. Operational SOPs, browsable online or clonable as an Obsidian vault.展开，提供了可运行的实现，对理解相关安全机制、工具原理与攻防技术具有较高的研究价值。

从技术实现角度看，此类项目的核心在于对底层原理的深入理解与工程化落地。开发者在研究过程中可以结合官方文档与社区讨论，梳理项目的初始化流程、核心模块职责与数据流转，逐步掌握其中的技术细节与设计思路。

使用与学习建议

1. 下载源码压缩包，解压到本地环境。

2. 根据项目类型准备对应的运行环境与依赖。

3. 按照 README 中的步骤完成配置与部署。

4. 在隔离的测试环境中运行验证，避免影响生产系统。

免责声明

本资源来源于开源社区，仅供安全研究、技术学习与合法授权范围内的攻防演练使用，请勿用于任何非法或侵害他人权益的用途。使用本项目产生的一切后果由使用者自行承担。