A super simple guide on how a tiny mistake by a web developer helped me solve Room 404 on TryHackMe.

En esta maquina veremos estos metodos de Explotacion a esta maquina

Lab Overview

At a glance Actor Mirage Kitten (also UNC1549, Smoke Sandstorm, Nimbus Manticore) Activity State-aligned cyber espionage and long-term network access Targets Aviation, defense, telecom, government…

CVE-2026-16347 lets attackers brute-force MikroTik RouterOS logins for unauthorized system access. Rated CVSS 8.8, with no fix yet. Apply mitigations. #MikroTik #RouterOS #CVE202616347 #BruteForce…

Introduction

A CTF Walkthrough on Insecure PyYAML Deserialization (yaml.load), Web App Enumeration, and Linux Process Reconnaissance.

Following the clues behind a covert HTTP Cookie exfiltration channel in a TryHackMe forensics challenge

Subdomain takeovers are one of those vulnerabilities that sound simple in theory but pay well in practice — and I recently found one on a…

alg=none x Attacker-Controlled Object Check

Exploring the Defensive Value of Modern Command-and-Control Research for Blue Teams, Red Teams, and Threat Hunters

Is your city’s water supply at risk from afar? It could be if the system is on the cloud. Hackers have targeted water systems in several US…

Unit 42 uncovered a threat actor using DeepSeek, Hermes Agent and public exploit tools to automate vulnerability research, target discovery…

∘ 1. Recover lost data ∘ 2. Digital Infidelity in the Modern Age ∘ 2.1 The Rise of Smartphone Secrets ∘ 2.2 Why Traditional Surveillance…

The Machine That Cannot Tell Who You Are

From HTML comment credential disclosure to YAML injection and privilege escalation through exposed service credentials.

This is a very easy room which involves Prompt Injection and LLM Security. I will be further attaching screenshots of how I completed this…

Build a Strong Foundation Before Diving into Cybersecurity

An anonymous attacker could fully enumerate, read, and overwrite the production customer-service attachment bucket of a major insurer’s…

How a seemingly harmless GraphQL query exposed private user history and highlighted the importance of authorization in nested resolvers.