All Security Engineering Courses

CVE-2025-54918-POC This GitHub project provides a proof-of-concept (POC) and technical demonstration for CVE-2025-54918, showcasing a security vulnerability in a system or application. It is intended for researchers and developers to understand the exploit mechanism and assess potential risks. 🔗 Link 🕹Subscribe to MalDev | GaK3r

🔎 Chkrootkit — охотник за руткитами на твоей системе Chkrootkit — лёгкий, но мощный сканер для Linux/Unix, который ищет следы руткитов, троянов и локальных эксплойтов. Быстро проверяет систему и сигнализирует о подозрительных файлах и процессах. Идеален, если:

🟢 нужно быстро проверить сервер без установки агентов 🟢 важен простой аудит безопасности 🟢 хочется понять, не скрываются ли в системе угрозы

⚙️ Ключевые возможности Chkrootkit:

🔵 Проверка известных руткитов и троянов 🔵 Сканирование системных процессов и модулей ядра 🔵 Поиск подозрительных бэкендов inetd, sshd, cron 🔵 Проверка ключевых бинарников на модификации 🔵 Лёгкий, работает без сети и демонов

⚡️ Быстрый старт с Chkrootkit: Установка:

sudo apt install chkrootkit        # Debian/Ubuntu  
sudo dnf install chkrootkit        # RHEL/CentOS  

Запуск сканирования:

sudo chkrootkit

📌 Что реально находит:

🟢 скрытые процессы и демоны 🟢 подменённые системные бинарники 🟢 следы популярных руткитов 🟢 подозрительные сетевые подключения 🟢 эксплойты локальных сервисов

Где использовать Chkrootkit:

🔴 Быстрый security-чек на прод-серверах 🔴 Регулярные проверки VPS и домашних серверов 🔴 В связке с Lynis, AIDE или auditd 🔴 Как baseline перед детальным pentest’ом

😈 CodeGuard: PySec Edition | Чат

🎃 PXEnum — системная разведка для Linux пентеста Братья по пентесту, нужен быстрый дамп всей системной информации. PXEnum — shell-скрипт собирает всё: пользователей, SUID, sudo history, SSH ключи, сервисы, версии софта.

Что дампит: Users + группы + home dirs Network interfaces + открытые порты RAM/CPU/BIOS info Sudoers + /etc/shadow права Bash/Python/Java версии Active processes + systemd сервисы

Установка (15 сек):

git clone https://github.com/shawnduong/PXEnum  
cd PXEnum  
chmod +x PXEnum.sh  
./PXEnum.sh  

После запуска — сразу видно: кто админ, какие SUID для privilege escalation, какие сервисы уязвимы. 🔗 Репозиторий 🖥 CodeGuard: Academy | Чат

🔄 🔍 Zircolite v2.40.0 Отличный инструмент для исследования логов, особенно крайне кривых и неудобных 💻 Windows EVTX Проводит анализ на основе SIGMA правил (основные идут в комплекте) Также работает с файлами .log, .xml, .json ⚙️ Установка:

git clone https://github.com/wagga40/Zircolite
cd Zircolite
pip3 install -r requirements.full.txt

Для Windows есть собранный бинарь Примеры:

python3 zircolite.py --evtx system.evtx
python3 zircolite.py --evtx system.evtx --ruleset rules/rules_windows_sysmon_pysigma.json
python3 zircolite.py --events auditd.log --ruleset rules/rules_linux.json --auditd
python3 zircolite.py --events sysmon.log --ruleset rules/rules_linux.json --sysmon4linux

Обновление правил:

python3 zircolite.py -U

🗂 Тестовый EVTX 💻 Home 💻 Sigma 📔 Documentation #dfir #forensics #zircolite #soft #python ✈️Join Us For More.... ‎ ‎🔥Telegram🔥: ‎https://t.me/SuBoXoneSoCiety ‎ ‎☠️Darkweb room☠️: http://suboxone2fzkkkeuezwozbbajgqargceo62wdx3f53awty6dv4mzzbad.onion ‎ ‎🫂Whatsapp community🫂 :https://whatsapp.com/channel/0029Vb7WAkz4tRrkdnGzzy25

Proxy-DLL-Loads This project demonstrates a proof of concept for intercepting and proxying DLL loads using undocumented Windows syscalls, enabling stealthy control over dynamic library loading. It's designed for advanced security research and potentially bypassing detection mechanisms. 🔗 Link 🕹Subscribe to MalDev | GaK3r

🔍 masscan — zmap на стероидах для портов masscan (https://github.com/robertdavidgraham/masscan) — самый быстрый сканер портов в мире. Сканирует весь интернет за минуты, не как nmap (5 дней). Идеален для начального recon'а. Полезен для bug bounty и инфраструктурного аудита:

🟢 Полный интернет за 6 минут: sudo masscan 0.0.0.0/0 -p80,443 --rate=1000000 🟢 Асинхронный скан: masscan 10.0.0.0/8 -p1-65535 --rate=10000 -oL results.txt 🟢 Только открытые: masscan target.com -p80,443 --open-only 🟢 Скриптинг: masscan 192.168.1.0/24 -p22 --banners -oG banners.grep 🟢 HTTP баннеры: masscan target -p80 --banners | grep -i server

⚙️ Установка:

git clone https://github.com/robertdavidgraham/masscan
cd masscan
make -j
sudo make install
# или sudo apt install masscan

🚀 Фичи vs nmap/zmap:

🔴Скорость: 10M+ пакетов/сек (nmap: 1-2k) 🔴Асинхронный I/O (не ждет ответы) 🔴Баннер grabbing из коробки 🔴Raw sockets (root-only, но скорость x100) 🔴Пауза/возобновление (--resume)

💡Prod-скрипт:

#!/bin/bash
masscan $1 -p80,443 --rate=50000 --open-only -oJ scan.json
cat scan.json | jq -r '.ip + ":" + (.ports[0].port|to_string)' > live_hosts.txt

Где юзают: Shodan-альтернатива, cloud pentest, mass subdomain enum. 👩‍💻 CodeGuard: Linux | Чат

OSSEC: лёгкий HIDS, если Wazuh слишком жирный ⌨️ OSSEC — это классический open-source HIDS, который стоит прямо на хосте, мониторит логи, файлы и реакции на инциденты. ​ Подходит, когда Elastic+Wazuh — оверкил, а тебе нужно просто видеть попытки взлома и критичные изменения в системе. ⚙️ Ключевые возможности OSSEC:

🔵Анализ логов системных сервисов, SSH, sudo, веб-серверов ​ 🔵File Integrity Monitoring для отслеживания изменений конфигов и бинарников​ 🔵Реакции на события: алерты, запуск скриптов, блокировки IP через firewall​ 🔵Поддержка множества ОС: Linux, *BSD, Windows, контейнеры и облако через агенты​ 🔵Интеграция с SIEM и внешними системами корреляции событий

⚡️Быстрый старт с OSSEC (агент + сервер): Установка сервера (Linux):

curl -O https://updates.atomicorp.com/channels/ossec/ossec-hids.tar.gz
tar -xzf ossec-hids.tar.gz
cd ossec-hids
sudo ./install.sh

Проверка статуса:

sudo /var/ossec/bin/ossec-control status

Подключение агента (на хосте):

curl -O https://updates.atomicorp.com/channels/ossec/ossec-hids-agent.tar.gz
tar -xzf ossec-hids-agent.tar.gz
cd ossec-hids-agent
sudo ./install.sh
/var/ossec/bin/manage_agents     # добавить агент на сервере
/var/ossec/bin/agent-auth -m <IP_OSSEC_SERVER>

Где использовать OSSEC:

🔴Малые и средние инфраструктуры без тяжёлого SIEM ​ 🔴Мониторинг критичных серверов (SSH, sudo, изменения конфигов)​ 🔴Как источник событий для уже существующего SIEM/лог-стека

😈 CodeGuard: PySec Edition | Чат

🔰 Learn web3.js | Introduction to Web3.js library Learn web3.js library 🗒 Description: Welcome to the Web3.js Course

This Web3.js course is designed for programmers and developers who want to take a comprehensive deep dive in building decentralized applications(dapp). This course provides detailed overviews of web3.js library and how to use web3.js library in order to interact with the blockchain and smart contract. In this course we are not just going to talk about Web3.js theory but also we are going to create a mini decentralized application (dapp) for practical.

EDRStartupHinder Prevents AV / EDR from running by redirecting a core DLL in the System32 folder to another location during Windows startup. Blog: https://www.zerosalarium.com/2026/01/edrstartuphinder-edr-startup-process-blocker.html

Zero Click, One NTLM: Microsoft Security Patch Bypass (CVE-2025-50154) CVE-2025-50154 allows an attacker to extract NTLM hashes without any user interaction, even on fully patched systems. By exploiting a subtle gap left in the mitigation, an attacker can trigger NTLM authentication requests automatically, enabling offline cracking or relay attacks to gain unauthorized access.

Obfusk8 now integrates a state-of-the-art Indirect Syscall mechanism to bypass User-Mode Hooks (EDRs/AVs) and static analysis checks. => "The Sorting Hat" Resolution: Instead of reading the .text section of ntdll.dll (which is often hooked or monitored), the engine parses the Export Directory. It filters functions starting with Zw, sorts them by memory address, and deduces the System Call Number (SSN) based on their index. This allows SSN resolution without ever touching executable code. => Lateral Gadget Execution: The engine does not contain the syscall (0F 05) instruction in its own binary. Instead, it locates a valid syscall; ret gadget inside ntdll.dll memory at runtime. Clean Call Stacks: A custom thunk is allocated that jumps to the ntdll gadget. To the OS kernel and security sensors, the system call appears to originate legitimately from ntdll.dll, maintaining a clean call stack. => Usage: Simply use K8_SYSCALL("ZwOpenProcess", ...) instead of NtOpenProcess. You have built a system that : 1 - Does not scan .text (Sorting Hat logic on Exports). 2 - Does not execute syscall locally (Lateral Gadget execution). 3 - Does not leave traces (Clean Call Stacks).

⚙️ ArgFuscator Приложение с открытым исходным кодом, которое помогает генерировать обфусцированные команды для 💻 Windows, 🐧 Linux и 💻 MacOS 🔗 ArgFuscator Invoke-ArgFuscator:

Install-Module -Name Invoke-ArgFuscator
Import-Module Invoke-ArgFuscator

Invoke-ArgFuscator -Command 'certutil /f /urlcache https://www.example.org/ homepage.txt'

Invoke-ArgFuscator -InputFile path\to\file.json

😹 Offline version #windows #obfuscator #redteam ✈️ Join Us For More.... ‎ ‎🔥Telegram🔥: ‎https://t.me/SuBoXoneSoCiety ‎ ‎☠️Darkweb room☠️: http://suboxone2fzkkkeuezwozbbajgqargceo62wdx3f53awty6dv4mzzbad.onion ‎ ‎🫂Whatsapp community🫂 :https://whatsapp.com/channel/0029Vb7WAkz4tRrkdnGzzy25

⏰🤖Real-Time Phishing Agents (Dynamic Phishing) ❓ why we use Real-time Phishing Agents (Dynamic Phishing) : When we relay on static templates the site will update continuously this will make the work more harder to Update the Phishing template every day, also if the user enabled MFA the full operation will fall down.. Because MFA code is temporary and we have 0 interaction with the Real Site to verify the token we got... That`s why the Dynamic Phishing Solve this matter. ℹ️ what is shown in the image above is example of Phishing operation in real time, where the attacker don`t relay on static template, instead its clone the server page in real-time , that`s will help the attacker to don`t relay on static templates and update it every day to mimic the real site. 😈 Adversary-in-the-Middle (AiTM): is a targeted, real-time phishing technique where the attacker operates a proxy between the victim and the legitimate service to intercept and manipulate the live authentication flow — capturing credentials, session cookies, tokens, or one-time codes so the attacker can immediately take over the session (often bypassing MFA). 🥷 attacker will capture credentials in real-time & often bypass MFA and that is the biggest advantage of Dynamic Phishing. 💻 Explain the attack Chain Using Evliginx2: 1. The Lure (Step 1) 🕷🔗: The victim clicks a phishing link (e.g., sent via email) that points to the attacker's domain: https://login.fakemicrosoft.com . The victim's browser sends a request to the Evilginx2 server, thinking it is the login page. 2. The Proxy Request (Step 2) 📶: Instead of serving a fake static page, the Evilginx2 server silently forwards that request to the real Microsoft login URL (https://login.microsoftonline.com). 3. Fetching the Real Site (Step 3) ™️🌐 : Microsoft's server receives the request. Thinking it's a normal user, it responds by sending the code for the actual login page back to the Evilginx2 server. 4. Displaying the Trap (Step 4) 🔼🔽: Evilginx2 takes that real login page and serves it to the victim. Crucial Detail: The victim sees the exact real login page because it is the real code, just served from the wrong domain (fakemicrosoft.com). 5. The Interception (Step 5) 💻 : The victim enters their username and password. These credentials are sent to the Evilginx2 server first, not Microsoft. The attacker now captures the password. 6. The Relay (Step 6)👊 : Evilginx2 immediately uses those stolen credentials to log in to the real Microsoft server on the backend. Note: If MFA (2FA) were required, Evilginx would prompt the user for the code here, capture it, and relay that too (this is the "Real-Time" aspect). 7. The Theft (Step 7 - The "Gold") ✅™️ : Microsoft accepts the valid credentials and replies with a Session Cookie (the digital token that proves you are logged in). Evilginx2 captures and saves this cookie. This is the main goal. With this cookie, the attacker can open their own browser, inject the cookie, and access the victim's account without needing the password or MFA again. 8. The Clean Exit (Step 8) 💻🏃‍♂️ : To avoid raising suspicion, Evilginx2 finally redirects the victim to a totally different website (or the actual Microsoft dashboard). The victim thinks they just logged in normally, or perhaps that the page glitched, while the attacker now has full access to the account.

⏰🤖Real-Time Phishing Agents (Dynamic Phishing) ❓ why we use Real-time Phishing Agents (Dynamic Phishing) : When we relay on static templates the site will update continuously this will make the work more harder to Update the Phishing template every day, also if the user enabled MFA the full operation will fall down.. Because MFA code is temporary and we have 0 interaction with the Real Site to verify the token we got... That`s why the Dynamic Phishing Solve this matter. ℹ️ what is shown in the image above is example of Phishing operation in real time, where the attacker don`t relay on static template, instead its clone the server page in real-time , that`s will help the attacker to don`t relay on static templates and update it every day to mimic the real site. 😈 Adversary-in-the-Middle (AiTM): is a targeted, real-time phishing technique where the attacker operates a proxy between the victim and the legitimate service to intercept and manipulate the live authentication flow — capturing credentials, session cookies, tokens, or one-time codes so the attacker can immediately take over the session (often bypassing MFA). 🥷 attacker will capture credentials in real-time & often bypass MFA and that is the biggest advantage of Dynamic Phishing. 💻 Explain the attack Chain Using Evliginx2: 1. The Lure (Step 1) 🕷🔗: The victim clicks a phishing link (e.g., sent via email) that points to the attacker's domain: https://login.fakemicrosoft.com . The victim's browser sends a request to the Evilginx2 server, thinking it is the login page. 2. The Proxy Request (Step 2) 📶: Instead of serving a fake static page, the Evilginx2 server silently forwards that request to the real Microsoft login URL (https://login.microsoftonline.com). 3. Fetching the Real Site (Step 3) ™️🌐 : Microsoft's server receives the request. Thinking it's a normal user, it responds by sending the code for the actual login page back to the Evilginx2 server. 4. Displaying the Trap (Step 4) 🔼🔽: Evilginx2 takes that real login page and serves it to the victim. Crucial Detail: The victim sees the exact real login page because it is the real code, just served from the wrong domain (fakemicrosoft.com). 5. The Interception (Step 5) 💻 : The victim enters their username and password. These credentials are sent to the Evilginx2 server first, not Microsoft. The attacker now captures the password. 6. The Relay (Step 6)👊 : Evilginx2 immediately uses those stolen credentials to log in to the real Microsoft server on the backend. Note: If MFA (2FA) were required, Evilginx would prompt the user for the code here, capture it, and relay that too (this is the "Real-Time" aspect). 7. The Theft (Step 7 - The "Gold") ✅™️ : Microsoft accepts the valid credentials and replies with a Session Cookie (the digital token that proves you are logged in). Evilginx2 captures and saves this cookie. This is the main goal. With this cookie, the attacker can open their own browser, inject the cookie, and access the victim's account without needing the password or MFA again. 8. The Clean Exit (Step 8) 💻🏃‍♂️ : To avoid raising suspicion, Evilginx2 finally redirects the victim to a totally different website (or the actual Microsoft dashboard). The victim thinks they just logged in normally, or perhaps that the page glitched, while the attacker now has full access to the account.

Nezha A legitimate open-source monitoring tool (post-exploitation RAT). Compatible with mainstream systems, including Linux, Windows, macOS, OpenWRT, and Synology. The agent provides SYSTEM/root level access, file management, and an interactive web terminal. VirusTotal shows 0/72 detections because it isn’t malware, it’s legitimate software pointed at attacker infrastructure. Installation is silent. Detection only occurs when attackers execute commands through the agent. Wiki: https://nezha.wiki/en_US/ Research: https://www.ontinue.com/resource/nezha-the-monitoring-tool-thats-also-a-perfect-rat/

TokenFlare Serverless AITM Simulation Framework for Entra ID and M365 Blog: https://labs.jumpsec.com/tokenflare-serverless-AiTM-phishing-in-under-60-seconds/