A compromised Linux server is not fixed by reinstalling: first you work out how they got in, then you look for the rest. A method for finding infected files with nothing but the shell, the signals you must not ignore, and why the order of operations matters more than the tools.
Read the article →What a SQL injection really is, why prepared statements eliminate it, and how to use OWASP ZAP and Burp Suite to look for it in a systematic way. With ethics and hacker identity: the difference between those who break things and those who help, written without jargon.
Read the article →The difference between free software and proprietary software is not the price, it is control. Why reading the code, being able to modify it and not depending on a vendor are worth more than any licence, and how all this came about from 1983 onwards.
Read the article →WordPress is the most widespread CMS in the world and the most fertile ground for anyone hunting for flaws. How vulnerabilities are actually hunted — from plugin recon to analysing patch diffs — and why the hard part is not finding them but understanding whether they are exploitable.
Read the article →A file with an appetising name, a false credential, a DNS that does not answer: none of this protects an asset, and yet it tells you who got in. The story and use of canary tokens, from cartographers to AWS containers.
Read the article →No software is immune, but almost everything we discover does not concern us. A practical guide to triage: reachability, exposure, real exploitability and the moment when the patch really goes before everything else.
Read the article →