If you’re at $0, you don’t need more knowledge. You need one working method and repetition.

API security When it comes to API Security and the attack surface our focus shifts from endpoints /login, /profile and the likes to objects, actions and trust assumptions within the API call An API …

Why Changing Your Password Doesn’t Always Evict an Attacker

One misplaced slash turned a file reader into a full filesystem browser

From data poisoning via anonymous S3 bucket to package hallucination supply chain attacks — here’s what conference research shows actually…

The world’s most widely used messaging platform is stepping into new territory. WhatsApp long known for its completely free core experience…

AirTouch HTB Writeup: Transparent Pivoting Without proxychains

Build SupplySecLab and learn to inspect models, audit dependencies, and govern LLM supply chains.

The premise of this challenge is to find 3 ingredients hidden in the system for a potion

In this writeup we solve the Dev Diaries room from TryHackMe using simple OSINT techniques The challenge shows how old snapshots public…

Understanding the Flow

“The boring findings pay the bills. The creative chains win the hall of fame.”

When JavaScript Hides the Vulnerability

Just finished studying about the Nature of Distributed Domain Name System.

-OWASP TOP 10 2025:IAAA FAILURES-
Task 1 — Introduction
Bu oda, 2025 yılının En Önemli 10 güvenlik kategorisinden 3 tanesini ele…

In this article, I will share the analysis process of a real incident via the “Alert Triage with Splunk” room on the TryHackMe platform.

Bu məqalədə mən TryHackMe platformasındakı “Alert Triage with Splunk” otağı üzərindən real bir insidentin analiz prosesini bölüşəcəm.

Difficulty: Medium Tags: DFIR, PowerShell, EVTX, Wireshark, C2, RC4, AES, CyberChef

*by Alborz Nazari*

## The problem nobody talks about

The ContAInment room: https://tryhackme.com/room/containment